JP7445477B2 - Vehicle management equipment and programs - Google Patents

Description

The present invention relates to a vehicle management device and a program.

Patent Document 1 states, ``When it is determined that a specific action by a passenger is an illegal act, the vehicle is directed to the nearest police station. Drive to the police station.''
[Prior art documents]
[Patent document]
[Patent Document 1] JP 2015-176444

In the first aspect of the present invention, the vehicle management device may include a reception unit that receives ride requests from users. The vehicle may include a travel plan management unit that creates a travel plan for allowing the user to board the motor vehicle based on the ride request. When information indicating that a user riding in a motor vehicle is determined to be a nuisance based on the drive plan is input, the drive plan management unit changes the drive plan to a user riding in a motor vehicle with a nuisance person. The user may be changed to ride in a different motor vehicle than other users.

The vehicle management device may further include a determination unit that determines whether the user is a nuisance. The travel plan management unit may manage a nuisance person's motor vehicle in which the nuisance person is allowed to ride, and other motor vehicles separately. When changing the travel plan, the travel plan may be changed so that the nuisance person is placed in a vehicle designated for the nuisance person.

When changing the travel plan, the travel plan management section may change the travel plan so that another user rides in another motor vehicle. The travel plan management unit manages the information identifying the motor vehicle in association with the rank, and may change to another motor vehicle of the same rank as the original motor vehicle.

The reception unit may receive an input of an evaluation of the troublesome person by another user. The user information storage unit may further include a user information storage unit that stores information indicating the degree of nuisance of the nuisance person in association with information for identifying the nuisance person based on the evaluation. The reception unit may prompt the user to input the evaluation after the troublesome person and the other user get into different motor vehicles. The reception unit may receive information regarding a travel plan other than information for identifying a nuisance person from another user, and may identify the nuisance person based on the information.

The travel plan management unit may output an instruction to the motor vehicle to prohibit the motor vehicle from traveling as long as the nuisance person is riding in the same motor vehicle as another user. The vehicle may further include a fee information output unit that outputs information on the user's usage fee according to the travel plan. The fee information output unit may output information indicating that a nuisance fee will be imposed on the troublesome person in addition to the usage fee.

In the second aspect of the present invention, a computer program may execute a reception procedure for accepting a ride request from a user. Based on the boarding request, a travel plan creation procedure may be executed to create a travel plan for allowing the user to board the motor vehicle. In the trip plan creation procedure, if information is input indicating that the user riding in the vehicle is determined to be a nuisance based on the trip plan, the trip plan is changed to The user may ride in a different motor vehicle than other users.

Note that the above summary of the invention does not list all the necessary features of the invention. Furthermore, subcombinations of these features may also constitute inventions.

1 conceptually shows a vehicle management system 70 to which this embodiment is applied. This is an example of a processing flow for processing boarding requests from users 50 and 52 in the vehicle management system 70. An example of functional blocks of the user terminal 40 is shown. This is an example of a boarding request input screen 410 displayed on the display unit 406. An example of functional blocks of the vehicle management device 10 is shown. An example of user information stored in the user information storage unit 104 is shown. An example of vehicle information 120 is shown. An example of travel plan information stored in the travel plan storage unit 108 is shown. An example of functional blocks of the motor vehicle 30 is shown. An example of travel plan information stored in the travel plan storage unit 306 is shown. This is an example of a processing flow in which the vehicle management system 70 executes a travel plan and settles fees. An example of the operation flow of troublesome person processing (S90) is shown. An example of the travel plan information overwritten in step S900 is shown. 12 illustrates an example computer 1200 in which aspects of the invention may be implemented, in whole or in part.

Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention according to the claims. Furthermore, not all combinations of features described in the embodiments are essential to the solution of the invention.

FIG. 1 conceptually shows a vehicle management system 70 to which this embodiment is applied. The vehicle management system 70 provides so-called MaaS, which seamlessly connects transportation by means of transportation other than private cars, such as car sharing and public transportation, as one service. In the vehicle management system 70, the vehicle management device 10, motor vehicles 30, 32, 34, and user terminals 40, 42 can communicate with each other via a network 20 such as the Internet.

The vehicle management device 10 is, for example, a server such as a personal computer. The automobiles 30, 32, and 34 are, for example, automobiles, and the driving method thereof does not matter. Furthermore, the motor vehicles 30, 32, and 34 may be passenger cars with a capacity of several people, or buses with a capacity of more than the passenger cars. The user terminal 40 is a communication terminal used by the user 50, for example, a smartphone. Similarly, user terminal 42 is used by user 52.

FIG. 2 is an example of a processing flow in which the vehicle management system 70 processes boarding requests from the users 50 and 52. The example of FIG. 2 shows an example in which the motor vehicle 30 is used in response to ride requests from both users 50 and 52.

The user terminal 40 receives an input of a ride request from the user 50 (S10). The user terminal 40 transmits a boarding request to the vehicle management device 10 (S12). The vehicle management device 10 creates a travel plan that satisfies the boarding request from the user terminal 40 (S14). Based on the creation of the travel plan, the vehicle management device 10 transmits reception information indicating that the ride request has been accepted to the user terminal 40 (S16), and also sends the vehicle scheduled to travel according to the travel plan to the user terminal 40 (S16). Information on the travel plan is transmitted to both vehicles 30 (S18).

Furthermore, when the vehicle management device 10 also receives a ride request from the user terminal 42 of the user 52 (S20, S22), it creates a travel plan (S42). In this case, the vehicle management device 10 creates a travel plan that also takes into consideration the travel plan created based on the boarding request from the user terminal 40.

In the example of FIG. 2, it is assumed that a travel plan including carpooling was created in step S24. Carpooling, also referred to as ride sharing, is when a motor vehicle in which a user is riding is traveling from the user's starting point to the destination, and another user also rides in the motor vehicle and shares the motor vehicle. It is something to do. In carpooling, the other user may get off the vehicle earlier than the previous user's destination, may get off the vehicle at the same destination, or may get off the vehicle further away.

The vehicle management device 10 transmits information on carpool candidates to the user terminal 40 of the user 50 who has sent the ride request first among the users 50 and 52 who are included in the trip plan and who have the possibility of carpooling (S26). ). The information on the carpool candidate includes, for example, information regarding the user 52 who is the carpool candidate partner. The user terminal 40 receives an input from the user 50 regarding whether or not carpooling is possible, and transmits it to the vehicle management device 10 (S28). In the example of FIG. 2, for the sake of simplicity, it is assumed that the user 50 has permitted carpooling.

Subsequently, the vehicle management device 10 transmits information on carpool candidates to the user terminal 42 of the user 52 who has transmitted the ride request later, among the users 50 and 52 who are included in the trip plan and who have the possibility of carpooling. (S30). The user terminal 42 receives an input from the user 52 regarding whether or not carpooling is possible, and transmits it to the vehicle management device 10 (S32). In the example of FIG. 2, to simplify the explanation, it is assumed that the user 52 also allows carpooling.

Based on the permission for carpooling from both users 50 and 52, the vehicle management device 10 transmits reception information indicating that the ride request has been accepted to each of the user terminals 40 and 42 (S34, S36). ), information on the travel plan is transmitted to the motor vehicle 30 scheduled to travel according to the travel plan (S38). Note that, unless otherwise specified, a method similar to that of known route guidance devices may be used to create the travel plan. Unless otherwise specified, a method for creating a travel plan when carpooling is added to a previous travel plan may be the same as that used for adding passing points to a travel route in known route guidance devices.

When you ride in the motor vehicle 30, if the person you ride with is a nuisance who causes a nuisance, you may feel uncomfortable and may even be injured. On the other hand, if there is a nuisance, there may be a method in which the doors of the motor vehicle 30 are locked and the vehicle 30 is moved to a predetermined location such as a police station. However, in that case, there is a problem in that the other user who is inconvenienced is also taken to the location. Therefore, in this embodiment, by appropriately responding to the troublesome person, the user who is causing the trouble can also be dealt with appropriately.

FIG. 3 shows an example of functional blocks of the user terminal 40. The user terminal 40 includes a communication section 402, an input section 404, and a display section 406. The communication unit 402 communicates with the vehicle management device 10 via the network 20 and transmits and receives information. The input unit 404 receives input of characters, numbers, etc. from the user 50. The display unit 406 displays images including characters, numbers, and the like. The input unit 404 and the display unit 406 may be integrated like a touch panel. The user terminal 42 may have the same configuration as the user terminal 40, and a description thereof will be omitted.

FIG. 4 is an example of a ride request input screen 410 displayed on the display unit 406. The request input screen 410 has input fields for the user ID, departure point, desired time, destination, desired time, number of fellow passengers, whether there are members of the opposite sex, whether there is smoking, and whether there will be food or drink. has. Of these, inputting the desired time for the destination is optional. In the example shown in FIG. 4, the user ID is "U0001," the departure point is "Aoyama X-△, Minato-ku, Tokyo," the desired time is "12/4 10:30," and the destination is "Chuo-X, Wako City, Saitama Prefecture." , the desired time has not been entered, there is only one passenger, there is no member of the opposite sex (that is, the passenger is a man of the same sex as the user), there is no smoking, and there is drinking alcohol.

The input unit 404 receives input from the user 50 in each input field, and displays the input information in the input field of the display unit 406. Among the input fields, text input is accepted for the user ID, etc., and selection/non-selection input is accepted for the opposite sex (these are so-called radio buttons). When the send button on the input screen 410 is pressed, the input information is sent from the communication unit 402 to the vehicle management device 10 as a ride request.

In addition to the input screen 410, the display unit 406 displays acceptance information indicating that the ride request has been accepted. It is preferable that the same information as the input screen 410 is displayed as the reception information so that it can be confirmed that the ride request has been accepted.

Furthermore, when the communication unit 402 receives information on carpool candidates from the vehicle management device 10, the display unit 406 displays this information and also displays an image prompting the user to input whether carpooling is possible. Furthermore, when the communication unit 402 receives usage fee information from the vehicle management device 10, the display unit 406 displays this information.

FIG. 5 shows an example of functional blocks of the vehicle management device 10. The vehicle management device 10 includes a reception section 102, a user information storage section 104, a trip plan management section 106, a trip plan storage section 108, a trip information acquisition section 110, a ride information acquisition section 112, and a fare information output section 114.

The reception unit 102 receives ride requests from the user terminals 40 and 42. The receiving unit 102 further receives information about the users 50 and 52 from the user terminals 40 and 42 prior to accepting the ride request or at the time of first accepting the ride request, and stores the information in the user information storage unit 104.

FIG. 6 shows an example of user information stored in the user information storage unit 104. As user information, the user's terminal ID, name, gender, age, user's face image, and annoyance level are stored in association with the user ID. The user ID may be designated by the users 50, 52, or may be automatically assigned when the reception unit 102 receives information from a new user. Furthermore, in the example of FIG. 6, an e-mail address that can be received by the terminal is stored as the terminal ID. The degree of annoyance will be discussed later.

In the example of FIG. 6, for example, in association with the user ID "U0001", the terminal ID "abc@edf.com", the name "Honda○ro", the gender "male", the age "32", an image file as a face image, A frequency of "3" is stored.

The travel plan management unit 106 of the vehicle management device 10 stores vehicle information 120 including the rank of the motor vehicle 30 and the like. According to the vehicle information 120, a vehicle for a troublesome person, in which a troublesome person is allowed to ride, and other vehicles are managed separately.

FIG. 7 shows an example of vehicle information 120. As the vehicle information 120, the vehicle type name, passenger capacity, and rank are stored in association with the vehicle ID. The rank is set in advance based on the size, horsepower, ride comfort, etc. of the vehicle. In the example of FIG. 7, the ranks are A, B, and Z in descending order, and rank Z indicates that the vehicle is dedicated to troublesome people. In more detail, vehicle ID "A30" is set to rank "A," vehicle ID "A32" is set to rank "B," vehicle ID "A34" is set to rank "Z," and the vehicle has the same passenger capacity of "5." However, this is an example where different ranks are set.

The travel plan management unit 106 creates a travel plan for the motor vehicles 30, 32, 34 based on ride requests from the users 50, 52. More specifically, the trip plan management unit 106 creates a trip plan based on information included in ride requests received from the user terminals 40 and 42. In this case, the trip plan management unit 106 reads user information stored in association with the user ID included in the ride request from the user information storage unit 104, and creates a trip plan using this information as well. do.

When creating a travel plan, the travel plan management unit 106 further uses the number of fellow passengers included in the boarding request and the capacity information in the vehicle information 120 to determine a motor vehicle. When determining a motor vehicle, the travel plan management unit 106 also refers to the rank of the vehicle information 120. In this case, the default is set to rank B, and when a request for an upgrade is included in the ride request, it is determined to use a vehicle of rank A. Or, conversely, the default may be set to rank A, and it may be determined to use a vehicle of rank B when there is a desire to downgrade in the ride request. In either case, between rank A and rank B, rank A may have a higher usage fee. The case where rank Z is used will be described later.

The travel plan management unit 106 stores information on the created travel plan in the travel plan storage unit 108, and transmits at least a portion of the information to the motor vehicles 30, 32, and 34 used in the travel plan. Furthermore, when the trip plan satisfies the ride request, the trip plan management unit 106 transmits acceptance information indicating this to the user terminals 40 and 42 that have transmitted the ride request. If the trip plan management unit 106 is unable to create a trip plan that satisfies the ride request, it transmits information indicating this to the user terminals 40 and 42 that have transmitted the ride request. Furthermore, when a trip plan that includes carpooling is created, the trip plan management unit 106 transmits information on carpooling candidates to the user terminals 40 and 42 of the users 50 and 52 who are likely to carpool.

FIG. 8 shows an example of travel plan information stored in the travel plan storage unit 108. Information on the trip plan includes the vehicle ID, carpool information, user ID, departure point, time, destination, driving route, time of arrival at the destination, number of fellow passengers, and the number of passengers of the opposite sex, in association with the trip ID. Information regarding presence/absence of smoking, presence/absence of drinking alcohol is stored.

The vehicle ID specifies the motor vehicle used in the travel plan specified by the travel ID. In the example of FIG. 8, since the vehicle ID "A30" is associated with the travel ID "D001", the vehicle specified by the vehicle ID "A30" in the travel plan, for example, the vehicle 30 in FIG. is used.

The carpooling information stores whether there is carpooling in the driving plan specified by the driving ID, and if there is carpooling, the driving ID of the driving partner's driving plan is stored. In the example of FIG. 8, the trip ID "D002" is stored in the carpool information column of the trip ID "D001," indicating that these are carpools. Note that if there is no carpooling, an invalid value "*****" is stored.

The user ID column stores the user ID that uses the travel plan specified by the travel ID. Note that when the motor vehicles 30, 32, and 34 are forwarded, that is, when none of the users board the vehicle, a user ID "U9999" indicating that the vehicle is forwarded is stored. In the example of FIG. 8, the user ID "U9999" is stored in correspondence with the travel ID "D003" indicating forwarding.

The fields of departure point, time, destination, number of fellow passengers, presence of the opposite sex, presence of smoking, and presence of alcohol are stored with information input by the users 50 and 52 identified by their user IDs in their ride requests. . The travel route stores information set by the travel plan storage unit 108 based on the departure point, time, destination, travel route, and other information. In FIG. 8, in order to simplify the explanation, it is simply indicated by letters such as "route S".

The destination time is stored as information predicted by the trip plan storage unit 108 based on the departure point, time, destination, travel route, and other information. Other information includes information on traffic congestion along the driving route. A known method may be used to set the travel route and predict the destination time.

In the case of forwarding, an invalid value "*" is stored as information on carpooling, time of departure, number of fellow passengers, presence or absence of members of the opposite sex, presence or absence of smoking, and presence or absence of alcohol consumption.

The driving information acquisition unit 110 of the vehicle management device 10 acquires information on the driving status of each of the motor vehicles 30, 32, and 34. An example of the driving situation information is information on the current locations of the motor vehicles 30, 32, and 34, which is obtained at regular intervals. Alternatively or in addition to this, the travel status information includes information as to whether each of the motor vehicles 30, 32, and 34 has arrived at the departure point in the corresponding travel plan, and information on whether each of the motor vehicles 30, 32, and 34 has arrived at the destination. It may also include information as to whether or not the request was made.

The riding information acquisition unit 112 acquires information indicating the riding situation from the motor vehicles 30, 32, and 34. An example of the information indicating the riding situation is an image of the inside of the motor vehicle 30, 32 that is obtained at regular intervals. Alternatively or in addition to this, the information indicating the riding situation may include information on whether the users 50, 52 are riding in the motor vehicle 30, 32, information on whether there is a fellow passenger, and information on whether or not there is a nuisance person. Information such as whether it is determined that there is a person may be included.

The charge information output unit 114 settles the usage charges for the users 50 and 52 who used the motor vehicles 30 and 32, and transmits the usage charge information to the corresponding user terminals 40 and 42. In this case, the fee information output unit 114 settles the usage fee based on the driving status information from the driving information acquisition unit 110 and the riding status information from the riding information acquisition unit 112.

FIG. 9 shows an example of functional blocks of the motor vehicle 30. The motor vehicle 30 includes an on-vehicle terminal 302, an automatic travel section 310, a current location information acquisition section 312, and a riding information acquisition section 314.

The in-vehicle terminal 302 includes a communication unit 304 that communicates with the vehicle management device 10 and a travel plan storage unit 306 that stores information on the travel plan that the communication unit 304 receives from the vehicle management device 10. In order to simplify the following explanation, it is assumed that the motor vehicle 30 is a vehicle capable of fully automated driving (sometimes referred to as level 5 automated driving). That is, an example will be described in which the automatic travel unit 310 executes driving tasks for all the motor vehicles 30 in accordance with the travel plan stored in the travel plan storage unit 306.

The current location information acquisition unit 312 includes, for example, GPS, and acquires information on the current location of the motor vehicle 30 at regular intervals. The current location information acquisition unit 312 associates the current location information with the traveling ID and transmits the current location information to the vehicle management device 10 at regular intervals. Alternatively or in addition to this, the current location information acquisition unit 312 refers to the current location information and the departure point and destination information stored in the trip plan storage unit 306 to determine when the departure point is reached. If the vehicle has arrived at the destination, information indicating that the vehicle has arrived at the destination may be transmitted to the vehicle management device 10 in association with the traveling ID.

The riding information acquisition unit 314 includes, for example, a camera that photographs the interior of the vehicle, and acquires images of the interior of the vehicle at regular intervals as information indicating the riding status of the motor vehicle 30. The ride information acquisition unit 314 associates the image with the travel ID and transmits the image to the vehicle management device 10 at regular intervals. Alternatively or in addition to this, the riding information acquisition unit 314 analyzes the image by image recognition or the like, and determines whether or not the users 50 and 52 are riding in the motor vehicle 30, whether there are fellow passengers or not, and whether or not they are causing trouble. It is also possible to determine whether there is a person present or not, and to send this information to the vehicle management device 10 as information on the riding situation in association with the traveling ID.

FIG. 10 shows an example of travel plan information stored in the travel plan storage unit 306. Among the travel plans generated by the vehicle management device 10, the travel plan storage unit 306 stores those using the own vehicle 30, that is, the travel plan with the vehicle ID "A30."

However, in addition to the ID itself, the user ID column receives and stores an image stored in the user information storage unit 104 of the vehicle management device 10. The boarding information acquisition unit 314 determines whether the users 50, 52 are on board, etc. by face authentication using the image.

FIG. 11 is an example of a processing flow in which the vehicle management system 70 executes the travel plan and settles the toll. The travel plan will be described using travel IDs "D001" and "002" in FIG. 10 of the motor vehicle 30 as an example.

First, the motor vehicle 30 automatically travels to the departure point of the travel ID "D001" of the travel plan stored in the on-vehicle terminal 302 of the motor vehicle 30 (S50). The current location information acquisition unit 312 compares the acquired current location of the motor vehicle 30 with the departure location of the travel plan, and if they match within a predetermined range, determines that the departure location has been reached, and the communication unit 304 This information is associated with the travel ID and transmitted to the vehicle management device 10 (S52).

The motor vehicle 30 waits until the boarding information acquisition unit 314 determines that the user 50 has boarded the vehicle using the image inside the vehicle and the image of the user 50 whose user ID is "U0001" corresponding to the travel plan (S54: No). If it is determined that the user 50 has boarded the vehicle (S54: Yes), the boarding information acquisition unit 314 transmits this to the vehicle management device 10 through the communication unit 304 in association with the traveling ID (S56).

The trip ID "D002" is a trip plan in which the driver will ride along with the motor vehicle 30 later. Therefore, for the travel plan as well, by repeating steps S50 to S56, the user 52 is allowed to share the ride.

The motor vehicle 30 continues to automatically travel toward the destination based on the travel plan (S58 and S60: No). The motor vehicle 30 determines whether or not there is a nuisance in the vehicle, and if there is a nuisance, the motor vehicle 30 and the vehicle management device 10 take action (S80 to S90). These operations will be described later.

The current location information acquisition unit 312 compares the acquired current location of the motor vehicle 30 with the destination of the travel plan, and if they match within a predetermined range, determines that the destination has been reached and stops the vehicle. , the communication unit 304 transmits this to the vehicle management device 10 in association with the travel ID (S60: Yes and S62).

The motor vehicle 30 waits until the boarding information acquisition unit 314 of the motor vehicle 30 determines that the user 50 has alighted from the vehicle using the image inside the vehicle and the image of the user 50 (S64: No). If it is determined that the user 50 has alighted (S64: Yes), the boarding information acquisition unit 314 transmits this information to the vehicle management device 10 through the communication unit 304 in association with the traveling ID (S66).

The fee information output unit 114 settles the usage fee (S75). In step S75, the fee information output unit 114 calculates the usage fee. The usage fee may be calculated using a predetermined formula based on the distance from the departure point to the destination, the time taken, the fuel or electricity used, the rank of the motor vehicle 30, and the like. The fee information output unit 114 transmits the fee information to the user terminal 40 (S76).

During automatic driving in step S58, the motor vehicle 30 determines in step S80 whether or not there is a nuisance in the vehicle. In this case, the boarding information acquisition unit 314 of the vehicle-mounted terminal 302 analyzes the image inside the vehicle and determines that there is a nuisance person when predetermined conditions are met. Examples of predetermined conditions include: the face is redder than the threshold value, the amount of movement in the vehicle is greater than the threshold value, the person is holding a dangerous object in their hand, etc.

In addition to or in place of this, the boarding information acquisition unit 314 may include a microphone to acquire the sound inside the vehicle, and determine that there is a nuisance person when a predetermined condition is met. Examples of predetermined conditions in this case include whether the volume of the voice is greater than a threshold, or whether specific words with threatening or obscene content are being uttered.

Instead of determining whether the images and/or sounds inside the vehicle match predetermined conditions, the ride information acquisition unit 314 may make the determination using a learning model that has been machine learned in advance. A convolutional neural network (CNN), a recurrent neural network (RNN), or the like may be used as the learning model.

If it is determined in step S80 that there is a nuisance in the vehicle (S80: Yes), the boarding information acquisition section 314 notifies the automatic traveling section 310 of this fact, and the automatic traveling section 310 stops (S82). In this case, it is preferable that the automatic travel unit 310 moves the motor vehicle 30 to a place where there is no problem in stopping the vehicle, such as the nearest public parking lot.

If it is determined in step S80 that there is a nuisance person, the ride information acquisition unit 314 identifies which travel plan the nuisance person boarded the vehicle with. For example, an image of a nuisance person and an image as a user ID associated with a travel plan are compared, and if they match at a predetermined degree of similarity, the user is considered to be a nuisance, and the user's travel plan is determined. Identify. Furthermore, even if the person who is a nuisance is not the user but a fellow passenger of the user, for example, it is possible to determine which person is the user's fellow passenger or not from images before and after the user gets on the ride, so it is possible to identify the person as a nuisance. The user who brought the passenger can be identified, and the travel plan can thereby be determined. As an example, the explanation will be continued assuming that the user 52 is determined to be a nuisance.

The boarding information acquisition unit 314 notifies the vehicle management device 10 of the presence of a nuisance person along with the parking position information and travel ID via the communication unit 304 (S84). The travel plan management unit 106 of the vehicle management device 10 performs the nuisance person processing (S90) when information indicating that there is a nuisance person in the motor vehicle 30 is input via the boarding information acquisition unit 112.

FIG. 12 shows an example of the operation flow of troublesome person processing (S90). Through the nuisance person processing (S90), the travel plan is changed so that the nuisance person and another user are to ride in different motor vehicles (S900).

In step S900, the trip plan management section 106 refers to the trip plan storage section 108 from the received trip ID to identify the trip ID that is shared with the received trip ID. In the example of FIG. 8, when the travel ID "D002" is received together with the information that there is a nuisance person, the travel ID "D001" is specified.

Further, the travel plan management unit 106 changes the travel plan so as to cancel carpooling and allocate a motor vehicle to each travel plan. For example, the nuisance person may be assigned a different vehicle, while other users may be assigned the same vehicle. In this case, the nuisance person is assigned a vehicle exclusively for the nuisance person, that is, a vehicle 34 of rank Z.

Further, the travel plan management unit 106 may not change the destination of the user 50 who is not a nuisance, but may forcibly change the destination of a nuisance user to a predetermined location. Preferably, the predetermined location is associated with a nuisance act that has been determined to be a nuisance. For example, if the face is redder than the threshold, there is a possibility that the person is causing a nuisance due to excessive drinking, so the nearest hospital is associated with the predetermined location. On the other hand, if the person is carrying a dangerous object in his or her hand, there is a possibility of injury or other criminal nuisance, so the nearest police station is associated with the predetermined location.

The travel plan management unit 106 notifies the original motor vehicle 30 and the newly assigned motor vehicle 34 of the changed travel plan (S900). The travel plan management unit 106 overwrites the changed travel plan in the travel plan storage unit 108.

The travel plan management unit 106 also sends to the motor vehicle 30 information regarding the changed travel plan of the motor vehicle 30, as well as information that the motor vehicle 30 is prohibited from driving until a new travel instruction is received. On the other hand, the travel plan management unit 106 informs the motor vehicle 34 of the changed travel plan of the motor vehicle 34 as well as information that the motor vehicle 34 will start driving after receiving a new instruction after reaching the parking position of the motor vehicle 30. Send.

Furthermore, the trip plan management unit 106 also notifies the user terminals 40 and 42 of the users 50 and 52, who are the parties to whom the trip plan has been changed, that the trip plan has been changed. In this case, a notification is sent to the user terminal 42 along with a display prompting the user to change trains, such as a message such as "We apologize for the inconvenience, but please change to the next vehicle to be dispatched." On the other hand, a notification is sent to the user terminal 40 to the effect that the carpool partner will be transferring, for example, along with a message such as "The carpool partner will be transferring to the next vehicle to be dispatched." The user terminals 40 and 42 can notify each of the users 50 and 52 of this by displaying the message on the display unit 406.

FIG. 13 shows an example of the travel plan information overwritten in step S900. In this trip plan, the trip plan in which "D001" and "D002" in FIG. ” has been overwritten. Furthermore, in the traveling ID "D002" of FIG. 8, the vehicle used was "A30", but it has been changed to "A34". In response to the fact that the user 52 with the travel ID "D002" was determined to be a nuisance, the vehicle 34 of rank Z was used as the vehicle for the user 52 and his fellow passengers to ride. This is due to a number of reasons.

The travel information acquisition unit 110 monitors whether the motor vehicle 34, which is the transfer vehicle of the nuisance person, has arrived at the stopping position of the motor vehicle 30 (S902). The arrangement of the motor vehicle 34 to the parking position is performed in the same manner as step S50 in FIG. 11.

If it is determined that the motor vehicle 34 has arrived at the parking position (S902: Yes), the riding information acquisition unit 112 monitors whether the nuisance person has transferred from the motor vehicle 30 to the motor vehicle 34 (S904). In this case, whether the nuisance person gets off the vehicle 30 can be determined in the same manner as in step S64, and whether the person getting into the vehicle 34 can be determined in the same manner as in step S52.

The motor vehicle 30 continues to stop based on instructions from the travel plan management unit 106 until it is determined that the nuisance person has transferred (S904: No). On the other hand, if it is determined that the troublesome person has transferred (S904: Yes), the motor vehicle 30 notifies the vehicle management device 10 of this fact, and based on this notification, the vehicle management device 10 instructs the motor vehicle 30 again. , the motor vehicle 30 resumes traveling based on the changed travel plan (S906).

The vehicle management device 10 instructs the motor vehicle 34 to start running after a predetermined period of time has elapsed (S908) from the start of the drive of the motor vehicle 30 (S906), thereby causing the motor vehicle 34 to stop running. Start (S910). The predetermined time is preferably the time required for the motor vehicle 30 to move away from the nuisance person riding in the motor vehicle 34 to such an extent that the motor vehicle 30 is no longer visible, and is, for example, about 5 to 10 minutes.

Furthermore, the reception unit 102 prompts the user 50 who is not a nuisance, that is, the user 50 who continues to be in the motor vehicle 30, to evaluate the user 50 as a nuisance (S912). In this case, the reception unit 102 causes the user terminal 40 of the user 50 to display a message such as "Please rate the degree of annoyance of the carpool partner you just transferred to on a five-point scale" in association with the user ID of the troublesome person. Submit information. However, it is preferable that information that identifies an individual, such as the user ID of the troublesome person, not be displayed on the user terminal 40.

The reception unit 102 receives a 5-level evaluation input into the user terminal 40 in association with the user ID of the person who is bothering the person, and determines the degree of nuisance of the person by referring to the evaluation ( S914). The receiving unit 102 stores the determined degree of annoyance in the annoyance degree column of the user information storage unit 104 (the same step). In this case, if the reception unit 102 receives an evaluation from a single user, the evaluation itself may be used as the nuisance level, or if it receives evaluations from multiple users, the reception unit 102 may use the average, maximum value, or The minimum value may be used as the nuisance level.

The reception unit 102 may further feed back the evaluation received from the user terminal 40 to the in-vehicle terminal 302 for determining the nuisance person. If the evaluation received by the user terminal 40 is higher than the predetermined threshold, it means that the judgment that the person is a nuisance was appropriate, and therefore the in-vehicle terminal 302 is instructed to strengthen the judgment. give feedback. Examples of feedback include changing the threshold value of a predetermined condition or changing the weighting of a machine learning learning model.

As described above, according to the present embodiment, when the partner of the carpool is a nuisance, the other users are transferred to a different vehicle from the other users, so the other users head to the destination in a comfortable condition as originally planned. be able to. Furthermore, as long as the troublesome person is riding in the same vehicle 30 as another user, the vehicle 30 is prohibited from running, so that the troublesome person can be encouraged to change trains.

Furthermore, since the troublesome person is forced to transfer to a dedicated rank Z motor vehicle 34, it is possible to suppress losses in the event that the motor vehicle is soiled or damaged. Furthermore, since evaluations from other users are accepted after the troublesome person has switched, troubles with the troublesome person over evaluations can be avoided.

Note that in step S900, instead of or in addition to having the nuisance person transfer, the travel plan may be changed so that another user who is not the nuisance person is transferred to another motor vehicle. In this case, the other motor vehicle is preferably of the same rank as the original motor vehicle, but may be upgraded considering the inconvenience caused.

In addition, in step S904, the vehicle management device 10 may send a message urging the user 52, who is the nuisance person or his/her fellow passenger, to change at regular intervals to the user terminal 42 of the user 52, who is the nuisance person or his or her fellow passenger, until the nuisance person transfers. Furthermore, the longer the transfer time, the greater the degree of inconvenience may be evaluated in step S914.

Further, in steps S906 and S910, the motor vehicles 30 and 34 resume running according to instructions from the vehicle management device 10. Alternatively, each of the in-vehicle terminals 302 of the motor vehicles 30 and 34 may decide to resume traveling by itself using the same judgment as in the above steps.

Further, in step S912, the reception unit 102 may receive a spontaneous evaluation from the user terminal 40. In this case, the receiving unit 102 receives from the user terminal 40 information related to the travel plan and identifying the nuisance person, such as a user ID, and identifies the nuisance person based on the information. An example of the information regarding the travel plan is the time when the troublesome person got on the vehicle. In this case, the reception unit 102 identifies the travel plan of the user 50 of the user terminal 40 that includes the time from the input of the time, with reference to the travel plan storage unit 108, and identifies the user of the carpooling travel plan in the travel plan. Identify the nuisance person by ID. Another example of the information regarding the travel plan is information that specifies the seat in the case where the travel plan includes the designation of the seat of the motor vehicle 30.

The degree of nuisance determined in step S914 may be further utilized. For example, the trip plan management unit 106 may determine whether to accept the ride request, whether to allow carpooling with other users, etc., depending on the degree of annoyance of the user who has made the ride request. Further, the travel plan management unit 106 may upgrade or downgrade the rank of the motor vehicle used in response to the ride request, depending on the degree of inconvenience to the user. Although the degree of annoyance is a negative evaluation, instead of or in addition to this, a positive evaluation indicating that the passenger is comfortable as a passenger may be used.

Further, in steps S26 and S30, it is preferable that the information on the degree of annoyance is always conveyed to the carpool candidate. That is, it is preferable that the degree of annoyance cannot be masked to the carpool candidate.

Further, the fee information output unit may output information indicating that a nuisance fee will be imposed on the troublesome person in addition to the usage fee.

In steps S52 and 62 in FIG. 11, the current location information acquisition unit 312 of the motor vehicle 30 determines whether or not it has arrived at the departure point and destination, and sends information indicating that it has arrived to the vehicle management device 10. . Instead, the current location information acquisition section 312 transmits the current location information to the vehicle management device 10, and the travel information acquisition section 110 of the vehicle management device 10 retrieves the information and the departure point stored in the travel plan storage section 108. By referring to the information on the departure point and the destination, it may be determined whether the departure point and the destination have been reached.

In steps S56 and S66 in FIG. 11, the boarding information acquisition unit 314 of the motor vehicle 30 determines whether the user 50 gets on or off the vehicle, and transmits information to that effect to the vehicle management device 10. Instead, the boarding information acquisition unit 314 transmits an image of the interior of the vehicle to the vehicle management device 10, and the boarding information acquisition unit 112 of the vehicle management device 10 retrieves the information and the user 50 stored in the user information storage unit 104. It may be determined whether the user 50 gets on or off the vehicle by analysis using the images.

When the seat of the user 50 in the motor vehicle 30 is designated, the boarding information acquisition unit 314 determines boarding and disembarkation based on whether a person is sitting in the seat using a sensor such as a load sensor provided on the seat. It's okay. As yet another example, the boarding information acquisition unit 314 may communicate with the user terminal 40 using short-range wireless communication such as WiFi or Bluetooth (registered trademark), and determine whether the user 50 is boarding the vehicle based on the availability of communication.

Similarly, in step S80 of FIG. 11, the passenger information acquisition unit 314 of the motor vehicle 30 determines whether there is a nuisance. Instead, the boarding information acquisition unit 314 transmits an image of the interior of the car to the vehicle management device 10, and the boarding information acquisition unit 112 of the vehicle management device 10 determines whether there is a nuisance person in the same manner as described above regarding step S80. may be determined and specified. In this case, the ride information acquisition section 112 functions as a determination section.

Furthermore, in place of or in addition to step S80, the presence or absence of a nuisance may be determined based on reports from other users 50, etc. who are riding together. An example of a notification is that a notification button provided on the motor vehicle 30 is pressed. Another example of the notification is that the user terminal 40 of the user 50 transmits to the in-vehicle terminal 302 or the vehicle management device 10 that there is a nuisance person.

In addition, if it is determined in step S80 that there is a nuisance person, before executing the nuisance person processing (S90), a warning is issued and a predetermined period of time is waited to see if the nuisance has subsided. You may also perform nuisance processing. Examples of the warning include displaying or audibly announcing this on the in-vehicle terminal 302, displaying or audibly announcing that on the user terminal 42 of the nuisance person or his fellow passenger, and the like.

Although the above-mentioned motor vehicles 30, 32, and 34 have been described as examples of vehicles capable of fully automatic operation, any or all of them may be vehicles that are not fully automatic. That is, the vehicle may be a vehicle (sometimes referred to as level 0 to 4 autonomous driving) in which a driver performs at least a portion of the driving tasks of the vehicle. The driver may be the user 50, 52. In this case, the driver may be responsible for some of the functional blocks shown in FIG.

Some or all of the functions of the vehicle management device 10 described above may be installed in the in-vehicle terminal 302. Thereby, the in-vehicle terminal 302 may function as the vehicle management device 10. In this case, the in-vehicle terminal 302 may create a travel plan for the own vehicle and settle the usage fee. Furthermore, when the vehicle-mounted terminal 302 changes the travel plan to one that also uses another motor vehicle 34 or the like, the vehicle-mounted terminal 302 may transmit the changed travel plan to the other motor vehicle 34 or the like.

Various embodiments of the invention may be described with reference to flowcharts and block diagrams, where the blocks represent (1) a stage in a process at which an operation is performed, or (2) a device responsible for performing the operation. may represent a section of Certain steps and sections may be implemented by dedicated circuitry, programmable circuitry provided with computer-readable instructions stored on a computer-readable medium, and/or a processor provided with computer-readable instructions stored on a computer-readable medium. It's fine. Specialized circuits may include digital and/or analog hardware circuits, and may include integrated circuits (ICs) and/or discrete circuits. Programmable circuits include logic AND, logic OR, logic Reconfigurable hardware circuits may include reconfigurable hardware circuits, including, for example.

A computer-readable medium may include any tangible device capable of storing instructions for execution by a suitable device, such that the computer-readable medium having instructions stored thereon is illustrated in a flowchart or block diagram. An article of manufacture will be provided that includes instructions that can be executed to create a means for performing the operations. Examples of computer readable media may include electronic storage media, magnetic storage media, optical storage media, electromagnetic storage media, semiconductor storage media, and the like. More specific examples of computer readable media include floppy disks, diskettes, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), Electrically Erasable Programmable Read Only Memory (EEPROM), Static Random Access Memory (SRAM), Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disk (DVD), Blu-ray (RTM) Disc, Memory Stick, Integrated Circuit cards etc. may be included.

Computer-readable instructions include assembler instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state configuration data, or object-oriented programming such as Smalltalk, JAVA, C++, etc. language, and either source code or object code written in any combination of one or more programming languages, including traditional procedural programming languages such as the "C" programming language or similar programming languages. good.

Computer-readable instructions may be implemented on a processor or programmable circuit of a general purpose computer, special purpose computer, or other programmable data processing device, either locally or over a wide area network (WAN), such as a local area network (LAN), the Internet, etc. ), computer-readable instructions may be executed to create a means for performing the operations specified in the flowchart or block diagrams. Examples of processors include computer processors, processing units, microprocessors, digital signal processors, controllers, microcontrollers, and the like.

FIG. 14 illustrates an example computer 1200 in which aspects of the invention may be implemented, in whole or in part. A program installed on computer 1200 may cause computer 1200 to function as an operation or one or more sections of an apparatus according to an embodiment of the present invention, or to perform one or more operations associated with an apparatus according to an embodiment of the present invention. Sections and/or computer 1200 may be caused to perform a process or a step of a process according to an embodiment of the invention. Such programs may be executed by CPU 1212 to cause computer 1200 to perform certain operations associated with some or all of the blocks in the flowcharts and block diagrams described herein.

Computer 1200 according to this embodiment includes a CPU 1212, RAM 1214, graphics controller 1216, and display device 1218, which are interconnected by host controller 1210. The computer 1200 also includes input/output units such as a communication interface 1222, a hard disk drive 1224, a DVD-ROM drive 1226, and an IC card drive, which are connected to the host controller 1210 via an input/output controller 1220. There is. The computer also includes legacy input/output units, such as ROM 1230 and keyboard 1242, which are connected to input/output controller 1220 via input/output chip 1240.

CPU 1212 operates according to programs stored in ROM 1230 and RAM 1214, thereby controlling each unit. Graphics controller 1216 obtains image data generated by CPU 1212, such as in a frame buffer provided in RAM 1214 or itself, and causes the image data to be displayed on display device 1218.

Communication interface 1222 communicates with other electronic devices via a network. Hard disk drive 1224 stores programs and data used by CPU 1212 within computer 1200. DVD-ROM drive 1226 reads programs or data from DVD-ROM 1201 and provides the programs or data to hard disk drive 1224 via RAM 1214. The IC card drive reads programs and data from and/or writes programs and data to the IC card.

ROM 1230 stores therein programs that are dependent on the computer 1200 hardware, such as a boot program that is executed by the computer 1200 upon activation. Input/output chip 1240 may also connect various input/output units to input/output controller 1220 via parallel ports, serial ports, keyboard ports, mouse ports, and the like.

A program is provided by a computer readable medium such as a DVD-ROM 1201 or an IC card. The program is read from a computer-readable medium, installed on hard disk drive 1224, RAM 1214, or ROM 1230, which are also examples of computer-readable media, and executed by CPU 1212. The information processing described in these programs is read by the computer 1200 and provides coordination between the programs and the various types of hardware resources described above. An apparatus or method may be configured to effectuate the manipulation or processing of information according to the use of computer 1200.

For example, when communication is performed between the computer 1200 and an external device, the CPU 1212 executes a communication program loaded into the RAM 1214, and sends communication processing to the communication interface 1222 based on the processing written in the communication program. You can give orders. The communication interface 1222 reads transmission data stored in a transmission buffer processing area provided in a recording medium such as a RAM 1214, a hard disk drive 1224, a DVD-ROM 1201, or an IC card under the control of the CPU 1212, and transmits the read transmission data. Data is transmitted to the network, or received data received from the network is written to a reception buffer processing area provided on the recording medium.

Further, the CPU 1212 causes the RAM 1214 to read all or a necessary part of a file or database stored in an external recording medium such as a hard disk drive 1224, a DVD-ROM drive 1226 (DVD-ROM 1201), an IC card, etc. Various types of processing may be performed on data on RAM 1214. The CPU 1212 then writes back the processed data to the external recording medium.

Various types of information, such as various types of programs, data, tables, and databases, may be stored on a recording medium and subjected to information processing. CPU 1212 performs various types of operations, information processing, conditional determination, conditional branching, unconditional branching, and information retrieval on data read from RAM 1214 as described elsewhere in this disclosure and specified by the program's instruction sequence. Various types of processing may be performed, including /substitutions, etc., and the results are written back to RAM 1214. Further, the CPU 1212 may search for information in a file in a recording medium, a database, or the like. For example, if a plurality of entries are stored in a recording medium, each having an attribute value of a first attribute associated with an attribute value of a second attribute, the CPU 1212 search the plurality of entries for an entry that matches the condition, read the attribute value of the second attribute stored in the entry, and thereby associate it with the first attribute that satisfies the predetermined condition. The attribute value of the second attribute may be acquired.

The programs or software modules described above may be stored on computer readable media on or near computer 1200. Additionally, a storage medium such as a hard disk or RAM provided in a server system connected to a dedicated communication network or the Internet can be used as a computer-readable medium, thereby providing the program to the computer 1200 via the network. do.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the range described in the above embodiments. It will be apparent to those skilled in the art that various changes or improvements can be made to the embodiments described above. It is clear from the claims that such modifications or improvements may be included within the technical scope of the present invention.

The order of execution of each process, such as the operation, procedure, step, and stage in the apparatus, system, program, and method shown in the claims, specification, and drawings, is specifically defined as "before" or "before". It should be noted that they can be implemented in any order unless the output of the previous process is used in the subsequent process. Even if the claims, specifications, and operational flows in the drawings are explained using "first," "next," etc. for convenience, this does not mean that it is essential to carry out the operations in this order. It's not a thing.

10 vehicle management device, 20 network, 30, 32, 34 motor vehicle, 40, 42 user terminal, 70 vehicle management system, 102 reception section, 104 user information storage section, 106 travel plan management section, 108 travel plan storage section, 110 Travel information acquisition unit, 112 Riding information acquisition unit, 114 Fare information output unit, 120 Vehicle information, 302 In-vehicle terminal, 304 Communication unit, 306 Travel plan storage unit, 310 Automated travel unit, 312 Current location information acquisition unit, 314 Riding information acquisition Department, 402 Communication Department, 404 Input Department, 406 Display Department, 410 Input Screen

Claims (10)

A reception department that accepts ride requests from users,
a travel plan management unit that creates a travel plan for causing the user to board the motor vehicle based on the ride request;
When information indicating that the user riding in the motor vehicle is determined to be a nuisance based on the driving plan is input, the driving plan management unit may change the driving plan to the nuisance person. and another user riding in the motor vehicle so that they ride in a different motor vehicle. The vehicle management device according to claim 1, further comprising a determination unit that determines whether the user is a nuisance. The travel plan management unit separately manages the nuisance vehicle in which the nuisance person is to ride and other vehicles, and when changing the travel plan, the nuisance person is transferred to the nuisance vehicle. The vehicle management device according to claim 1 or 2, wherein the vehicle management device is changed to allow the vehicle to be boarded. The vehicle management device according to any one of claims 1 to 3, wherein the travel plan management section changes the travel plan so that the other user rides in another motor vehicle when changing the travel plan. The vehicle management device according to claim 4, wherein the travel plan management unit manages information identifying a motor vehicle in association with a rank, and changes to the other motor vehicle having the same rank as the original motor vehicle. . The reception unit receives an input of an evaluation of the troublesome person by the other user,
The vehicle according to any one of claims 1 to 5, further comprising a user information storage unit that stores information indicating the degree of nuisance of the nuisance person in association with information for identifying the nuisance person based on the evaluation. Management device. The vehicle management device according to claim 6, wherein the reception unit prompts the user to input the evaluation after the nuisance person and the other user board different motor vehicles. 8. The driving plan management unit outputs an instruction to the motor vehicle to prohibit the motor vehicle from traveling as long as the nuisance person is riding in the same motor vehicle as the other user. The vehicle management device according to item 1. further comprising a fee information output unit that outputs information on usage fees of the user according to the travel plan,
The vehicle management device according to any one of claims 1 to 8 , wherein the fee information output unit outputs information indicating that a nuisance fee will be imposed on the troublesome person in addition to the usage fee. A reception procedure for accepting a ride request from a user on a computer,
executing a travel plan creation procedure for creating a travel plan for causing the user to board the motor vehicle based on the ride request;
In the travel plan creation procedure, if information indicating that the user riding in the motor vehicle is determined to be a nuisance based on the travel plan is input, the travel plan is and another user riding in the motor vehicle so that they ride in a different motor vehicle.

Images