Vehicle management device, vehicle management system, vehicle management method, and program

Abstract

We provide services to users of vehicles currently in use that can adapt to a variety of changes in their usage patterns. [Solution] The vehicle management device includes a determination unit that determines whether the current location, return location, or route between the current location and the return location of a vehicle to be shared or leased is in a location where special circumstances exist; a notification unit that, when it is determined that the current location, the return location, or the route is in a location where special circumstances exist, notifies that the vehicle is in a location where special circumstances exist; and a setting unit that sets the return location according to the vehicle's mobility status.

Description

Technical Field

[0001] The present invention relates to a vehicle management device, a vehicle management system, a vehicle management method, and a program.

Background Art

[0002] Conventionally, services that allow the use of vehicles have been widely provided in the form of sharing services, rental car services, etc. In this way, for example, a service that charges for the time of using a vehicle and provides the vehicle is known.

[0003] In conventional services, a vehicle management server that manages a vehicle by performing information communication between an information processing device connected to a communication line and the vehicle may be used. Specifically, the vehicle management server first acquires current position data from a vehicle being rented. Next, the vehicle management server acquires data such as performance, return location, and scheduled return time. Based on these data, the vehicle management server searches for a time-strict route, the fastest route, etc., and provides the route to the vehicle. In this way, in a car-sharing service, a technique for providing navigation information so that the scheduled return time is observed is known (see, for example, Patent Document 1, etc.).

[0004] Also, first, the vehicle management server acquires current position data from a vehicle targeted for the service in association with time data. Next, the vehicle management server acquires data such as traffic jam information, returnable area, and scheduled return time. Based on these data, the vehicle management server provides a returnable area. In this way, in a car-sharing service, a technique for providing a returnable area is known (see, for example, Patent Document 2, etc.).

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Patent Document 2

[0006] Conventional technologies have shortcomings in their ability to adequately account for vehicle usage in the event of accidents, weather conditions, or natural disasters. Therefore, there is a challenge in providing services that better anticipate special circumstances such as accidents, weather conditions, or natural disasters.

[0007] The present invention aims to provide users of vehicles in use with a service that can respond to a variety of changes in their usage conditions. [Means for solving the problem]

[0008] To solve the above problems, a vehicle management device in one aspect of the present invention is: A determination unit that determines whether the current location of a vehicle to be shared or leased, the return location, or the route between the current location and the return location is in a location where special circumstances exist, When it is determined that the current location, the return location, or the route is in a location where the special circumstances are occurring, a notification unit provides a notification indicating that the vehicle is in a special situation. A setting unit sets the return location according to the mobility status of the vehicle. It is characterized by having the following features. [Effects of the Invention]

[0009] According to the present invention, it is possible to provide users of vehicles in use with services that can respond to a variety of changes in their usage conditions. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows an example of a system configuration. [Figure 2] This figure shows an example of a hardware configuration. [Figure 3] This figure shows the first example of the overall processing. [Figure 4] It is a diagram showing the first notification example. [Figure 5] It is a diagram showing the second notification example. [Figure 6] It is a diagram showing the first example of determining whether movement is possible. [Figure 7] It is a diagram showing the second example of determining whether movement is possible. [Figure 8] It is a diagram showing the second example of overall processing. [Figure 9] It is a diagram showing an example of a target for judging special circumstances. [Figure 10] It is a diagram showing an example in which the current location, the return location, and the route are targets for judgment. [Figure 11] It is a diagram showing an example of a functional configuration.

Mode for Carrying Out the Invention

[0011] Hereinafter, specific examples will be described with reference to the attached drawings. In the following description, the reference numerals described in the drawings refer to the same elements. Also, the embodiments are not limited to the following specific examples, and the embodiments may include elements other than those shown in the drawings.

[0012] The "vehicle" is, for example, a four-wheeled automobile such as a passenger car. However, the vehicle may be any moving body that is the subject of sharing or lending, regardless of the presence or absence of a prime mover, size, number of passengers that can be carried, or structure. The vehicle is, for example, a "vehicle" corresponding to item 8 of paragraph 1 of Article 2 of the Road Traffic Law (Law No. 105 of 1960). Hereinafter, a four-wheeled automobile will be described as an example.

[0013] "Sharing" is, for example, in a sharing service (also referred to as "car sharing", "car sharing ring", or simply "sharing", etc. The vehicle that is the subject of the service is also referred to as a "sharing car", etc.), a service format used by a plurality of people (for example, "members" who are registered in advance for the service).

[0014] "Lending" is, for example, in a rental service (also referred to as "car rental service" or simply "rental", etc.), a service in which a user borrows and uses a vehicle from a company that provides the service.

[0015] "Sharing" and "lending" are different in that, for example, "lending" is a service that lends a vehicle to a user for a fee and charges by the hour, day, or month, while "sharing" is a service that coordinates a specific vehicle among members and the user borrows it at the time they want to use it. However, in this application, "sharing" or "lending" is not limited to the services with the above names, and any vehicle that is used by adjusting the usage time, etc. through reservation, etc. among multiple users is acceptable. Therefore, the fee is not limited to charging by the hour, etc. or the frequency of use, etc., and may be a fixed amount, etc., regardless of the form of the fee.

[0016] Hereinafter, a sharing service shared by multiple users and an example of a shared car that is the target of the sharing service will be described.

[0017] [Example of System Configuration] FIG. 1 is a diagram showing an example of a system configuration. For example, the sharing service provides the service through a vehicle management system 100 with the following configuration.

[0018] The vehicle management system 100 is composed of information processing devices such as a server 101 and an in-vehicle unit 102, for example. However, the vehicle management system 100 may further have devices other than the server 101 and the in-vehicle unit 102. Hereinafter, for the sake of explanation, an example in which the vehicle management system 100 is composed only of the server 101 and the in-vehicle unit 102 will be described.

[0019] The vehicle management system 100 manages, for example, a station 200 and vehicles that use the station 200. Hereinafter, an example in which the vehicle management device is the server 101 will be described. However, the vehicle management device may be an information processing device other than the server 101 or a plurality of information processing devices.

[0020] Station 200 is, for example, a parking lot. However, Station 200 is not limited to a parking lot; it may also be a part of a road (for example, when providing a so-called "street car-sharing" service, referring to a car-sharing station on the road space), a garage, or part of a building. In other words, Station 200 just needs to be a space where services such as parking and retrieving vehicles 201, etc., can be provided.

[0021] The following explanation assumes that station 200 is a parking lot. Therefore, station 200 may have devices used for management, such as a payment machine 202. For example, the payment machine 202 connects to server 101 and sends and receives data.

[0022] The following explanation uses an example where a shared service is provided to user 203 at station 200. Specifically, before using the shared service, user 203 enters into a contract with the company or other entity managing station 200 to use the shared service. Hereafter, this state in which the shared service becomes available through such a contract will be referred to as the "registered" state.

[0023] Registration is the process of becoming a member of the shared service. It involves entering the required information, and once server 101 recognizes the registered user 203, the shared service becomes available. Note that the registration process varies depending on the pre-configured contract details.

[0024] For example, registration is performed using an information processing terminal 204 owned by user 203. Hereinafter, it is assumed that user 203 always wears the information processing terminal 204 while using the shared service. Therefore, if the information processing terminal 204 stores identification information, user 203 will be recognized as a member by the server 101, etc., based on the identification information. However, whether or not user 203 is registered may be recognized by, for example, facial recognition, password, or an identification (ID) card, and does not require the use of the information processing terminal 204.

[0025] Station 200 is managed unmanned, meaning that no employees of the company providing the shared services are permanently stationed there. However, it is also permissible for a manager or other person to be present at Station 200 to provide services in a manned manner.

[0026] In a shared service, for example, user 203 starts using the service from station 200. That is, when user 203 goes to station 200, they can use one of the parked vehicles as part of the shared service. Therefore, station 200 becomes the "starting point" of the shared service. On the other hand, the shared service ends after the user leaves the starting point, for example, when they return vehicle 201 to the "returning point".

[0027] However, the start and return of the shared service may be done through other procedures. Also, the starting and returning locations are not limited to Station 200; for example, the user 203 may designate the starting or returning location, or a location designated by the company providing the shared service. For example, the return location may be a "declared location" designated by the user 203, rather than Station 200.

[0028] In the following example, the shared service is set up so that Station 200 serves as both the starting point and the return point at the start of the service. In other words, in principle, User 203 is obligated to return the shared service to Station 200, where the service was initiated.

[0029] [Example Hardware Configuration] Figure 2 shows an example of a hardware configuration. Server 101 and in-vehicle unit 102 are devices with the following hardware configuration, for example.

[0030] Server 101 is an information processing device that includes, for example, a Central Processing Unit (hereinafter referred to as "CPU 101H1"), a storage device 101H2, an input device 101H3, an output device 101H4, and a communication device 101H5.

[0031] CPU101H1 is an example of an arithmetic unit and control unit. Therefore, CPU101H1 works in cooperation with memory device 101H2 and other components to perform various processes and control hardware.

[0032] The storage device 101H2 includes the main memory and auxiliary storage devices, etc.

[0033] The input device 101H3 is a device that receives input from the operator. For example, the input device 101H3 may be a keyboard or a mouse.

[0034] The output device 101H4 is a device that outputs processing results, etc., to the operator. For example, the output device 101H4 is a display, etc.

[0035] The communication device 101H5 is a device that communicates with the external device 205. For example, the communication device 101H5 includes an antenna or a connector. The communication device 101H5 also includes functions for processing (transmitting and receiving) and signal processing for communication.

[0036] Server 101 is installed, for example, in the management office or call center of a company providing a shared service. Therefore, server 101 is operated, for example, by an administrator of the company providing the shared service. However, a management office or call center is not mandatory, and the location where server 101 is installed does not have to be a management office or call center.

[0037] The in-vehicle unit 102 is hardware installed in the shared object (i.e., a vehicle) when a company provides a sharing service. The in-vehicle unit 102 is installed inside a vehicle 201, for example. The in-vehicle unit 102 is typically an information processing device that includes a CPU 102H1, a storage device 102H2, an input device 102H3, an output device 102H4, and a communication device 102H5, etc.

[0038] For example, the CPU 102H1, storage device 102H2, input device 102H3, output device 102H4, and communication device 102H5 are similar to the CPU 101H1, storage device 101H2, input device 101H3, output device 101H4, and communication device 101H5. On the other hand, the in-vehicle unit 102 differs from the server 101 in that it is further equipped with a position sensor 102H6.

[0039] The position sensor 102H6 is a sensor that generates position data indicating the current location of the vehicle 201. Specifically, the position sensor 102H6 generates position data indicating latitude and longitude based on the Global Positioning System (hereinafter referred to as "GPS") or the Quasi-Zenith Satellite System (QZSS), etc. However, the position sensor 102H6 is not limited to generating position data based on GPS, etc., but may also generate position data by determining the current location via short-range communication or wireless communication, etc.

[0040] The in-vehicle unit 102 is connected to a so-called car navigation system, and functions as a means of displaying information to the user and a means of receiving user operations via the car navigation system's display device. The configuration of the in-vehicle unit 102 may be integrated into the so-called car navigation system. Alternatively, the in-vehicle unit 102 may be a smartphone or the like temporarily placed inside the vehicle.

[0041] The information processing terminal 204 is, for example, a smartphone, a mobile phone, or a mobile computer. The information processing terminal 204 is an information processing device equipped with a CPU 204H1, a storage device 204H2, an input device 204H3, an output device 204H4, a communication device 204H5, and a position sensor 204H6. For example, the CPU 204H1, storage device 204H2, input device 204H3, output device 204H4, communication device 204H5, and position sensor 204H6 are similar devices to the CPU 102H1, storage device 102H2, input device 102H3, output device 102H4, communication device 102H5, and position sensor 102H6.

[0042] However, the in-vehicle unit 102 and the information processing terminal 204 do not necessarily have the same hardware configuration.

[0043] The in-vehicle unit 102 may be replaced by, for example, an information processing terminal 204 with pre-installed application software. Furthermore, there may be multiple units of each device.

[0044] The server 101, the in-vehicle unit 102, and the information processing terminal 204 are not limited to the hardware configuration described above. For example, the server 101, the in-vehicle unit 102, and the information processing terminal 204 may further include, in addition to the above hardware, an arithmetic unit, a control unit, a storage device, an input device, an output device, a communication device, a sensor, or an auxiliary device, either internally or externally.

[0045] The server 101, the in-vehicle unit 102, and the information processing terminal 204 may communicate with an external device 205, etc., via a network. For example, the external device 205 is an information processing device managed by an administrative agency such as the Japan Meteorological Agency. Therefore, the server 101, the in-vehicle unit 102, and the information processing terminal 204 can obtain various types of information such as weather information, traffic information, or disaster information from the external device 205, etc.

[0046] [Overall processing example] Figure 3 shows a first example of the overall processing. For example, the overall processing is primarily executed by server 101, as shown below.

[0047] In step S10, server 101 starts the service. For example, the share service is started based on an operation by user 203 or an operation by an operator in the control room. When the share service starts, for example, hourly billing begins (time is measured for billing purposes, etc.), or a management program is launched. The processes to be executed when the service starts are pre-configured.

[0048] The following explanation uses an example where the service terminates simultaneously with the completion of the overall process. Therefore, each process that makes up the overall process described below is executed while the shared service is running.

[0049] Furthermore, during the operation of the shared service, user 203 may contact the call center by phone regarding any problems or issues.

[0050] In step S20, the server 101 determines whether or not special circumstances have occurred. For example, the determination of whether or not special circumstances have occurred is made when the server 101 acquires information from an external device 205, etc., and if the acquired information contains information indicating that a disaster of a certain scale has occurred, it is determined that special circumstances have occurred.

[0051] Server 101 determines whether special circumstances have occurred by referring to information from an external device 205 or a pre-established database. For example, Server 101 obtains location data from the in-vehicle unit 102 or the information processing terminal 204 to determine the current location of the vehicle 201. Then, based on the external device 205 or the database, Server 101 determines the current location and the weather conditions (including seismic intensity, rainfall, climate, temperature, humidity, atmospheric pressure, flood occurrence status, etc.), traffic conditions, or altitude of the surrounding area. The determination of special circumstances is predetermined, depending on the nature and accuracy of the special circumstances, and what information is to be obtained and how the determination is made.

[0052] Hereinafter, data indicating information used to determine whether or not special circumstances have occurred will be referred to as "circumstance data." For example, the server 101 acquires the circumstances data from an external device 205 (which may include information on the internet, etc.) or from a sensor, etc. What kind of circumstances data to acquire is, for example, set in advance.

[0053] Furthermore, the context data does not need to be used uniformly in the decision-making process. That is, among multiple context data, data containing information of high importance may be given higher weight in the decision-making process. For example, context data obtained from highly reliable sources may be set to contain information of high importance. Specifically, context data obtained from government agencies, etc., may be set to be data from highly reliable sources. On the other hand, context data obtained from, for example, SNS (Social Networking Service), may be set to be data from unreliable sources. This is an example of determining importance based on the source from which the context data is obtained. Alternatively, context data related to earthquakes may be set to be of high importance, and context data related to rainfall may be set to be of moderate importance, etc. This is an example of determining importance based on the duration of the impact when a special event occurs. In this way, assigning weights to context data can improve the accuracy of the decision-making process.

[0054] However, the determination of whether or not special circumstances have occurred may be made based on operations by user 203, operations by employees of companies providing services such as call centers, or operations by operators in the control room.

[0055] Furthermore, special circumstances may be determined separately for each area designated in advance. For example, an area could be the area corresponding to the information to be acquired, a region, country, or prefecture designated in advance by the administrator, etc. By determining special circumstances separately for each area in this way, it is possible to reflect circumstances appropriate to each area.

[0056] In addition, special circumstances may be determined at regular intervals or when a sensor detects a disaster. Thus, the trigger for determining special circumstances, i.e., the trigger for executing step S20, may have set execution conditions.

[0057] If it determines that special circumstances have occurred (YES in step S20), server 101 proceeds to step S30. On the other hand, if it determines that no special circumstances have occurred (NO in step S20), server 101 proceeds to step S40.

[0058] If it is determined that special circumstances have occurred (YES in step S20), the vehicle management system 100 will enter "disaster mode". On the other hand, if it is determined that no special circumstances have occurred (NO in step S20), the vehicle management system 100 will enter "normal mode". In this way, the vehicle management system 100 switches modes based on the determination of special circumstances.

[0059] The mode is a state that the vehicle management system 100 refers to when executing various processes. For example, using "normal mode" as the baseline, in "disaster mode," the vehicle management system 100 switches to perform disaster-related processing. How the operation changes depending on the mode is set in advance.

[0060] In step S30, server 101 issues a notification (hereinafter sometimes simply referred to as "notification") indicating that there are special circumstances. Specifically, server 101 displays a message on the display or elsewhere indicating that a disaster has occurred, informing user 203 that there are special circumstances. For example, the notification is made as follows:

[0061] [Example of a notification] Figure 4 shows an example of the first notification. For example, the notification is a process that displays a message box 300 or the like on the display device of the car navigation system connected to the in-vehicle unit 102, based on a notification from the server 101.

[0062] For example, in "normal mode," that is, when there is no disaster, the in-vehicle unit 102 displays a map display 301 on the screen for the car navigation service. On the other hand, when it enters "disaster mode," the in-vehicle unit 102 sends a notification via a message box 300 or the like. When a notification is sent in this way, the user 203 can be informed that a disaster has occurred.

[0063] Furthermore, notifications are not limited to messages or images. For example, notifications may be output in formats other than those from the in-vehicle unit 102, such as audio output including warning sounds, or flashing of LEDs (Light Emitting Diodes).

[0064] Furthermore, it is desirable to limit notifications to vehicles that meet certain conditions, rather than to all vehicles under management. For example, if special circumstances are judged on an area-by-area basis, notifications should be sent to vehicles within the area where special circumstances are determined to have occurred. By limiting notifications to vehicles that are highly likely to have experienced special circumstances, rather than all vehicles, it is possible to prevent vehicles that have not been affected by a disaster from entering "disaster mode."

[0065] Figure 5 shows a second example of a notification. For example, the notification is a process that displays a pop-up display 302, etc., on the information processing terminal 204 based on a notification from the server 101.

[0066] When "disaster mode" is activated, the information processing terminal 204 will notify the user via a pop-up display 302 or the like. However, the notification may also be sent via email, SMS (Short Message Service), or output by application software.

[0067] Once the notification is sent as described above, server 101 can inform user 203 that a disaster or other incident has occurred.

[0068] On the other hand, if it is determined that no disaster or other incident has occurred, that is, that no special circumstances have occurred (NO in step S20), the vehicle management system 100 will enter "normal mode" and perform the following processing.

[0069] In step S40, server 101 continues the service. For example, if the target vehicle 201 is currently located outside the area where the disaster or other incident has occurred, server 101 will enter "normal mode" (if the initial setting of the mode is "normal mode", the mode will be maintained). Therefore, server 101 continues to provide the shared service.

[0070] On the other hand, if a disaster or other emergency occurs, that is, if it is determined that an emergency has occurred (YES in step S20), the vehicle management system 100 enters "disaster mode" and performs the following processing after step S30.

[0071] In step S50, the server 101 determines whether the vehicle 201 is movable or not. For example, the determination of whether the vehicle 201 is movable or not is made as follows:

[0072] [Examples of decisions regarding whether movement is permitted] Figure 6 shows a first example of determining whether or not movement is possible. For example, in determining whether or not vehicle 201 is movable, the in-vehicle unit 102 displays an input button 303 on its display.

[0073] The input button 303 is an example of a GUI (Graphical User Interface) that prompts user 203 to input the result of determining whether or not vehicle 201 is capable of self-propulsion.

[0074] For example, the input button 303 outputs a message such as "Can you drive the vehicle to the nearest parking lot?" to the user 203, asking whether the vehicle 201 is still drivable despite damage from the disaster or disruption of the transportation network caused by the disaster.

[0075] In addition, in this example, the input button 303 prompts user 203 to input whether vehicle 201 can travel to station 200. Specifically, the input button 303 has a "movable" button and a "not movable" button. When user 203 presses the "movable" button, server 101 receives information that, according to user 203's judgment, vehicle 201 is movable. On the other hand, when user 203 presses the "not movable" button, server 101 receives information that, according to user 203's judgment, vehicle 201 is not movable.

[0076] Figure 7 shows a second example of determining whether or not a vehicle 201 is movable. For example, when determining whether or not a vehicle 201 is movable, the input of the determination by user 203 may be performed on the information processing terminal 204.

[0077] When using the information processing terminal 204, the input button 303 is displayed on the information processing terminal 204, just as it is when using the in-vehicle unit 102. Specifically, when using the information processing terminal 204, a message is output to the user 203 asking whether the vehicle 201 is still able to move under its own power due to damage from the disaster or destruction of the transportation network caused by the disaster.

[0078] Furthermore, the input button 303 may also have a "drivable" button for inputting the result that the vehicle 201 is capable of self-propulsion, and a "not drivable" button for inputting the result that the vehicle 201 is not capable of self-propulsion.

[0079] Therefore, when user 203 presses the "Can drive" button on the information processing terminal 204, server 101 receives information that, according to user 203's judgment, vehicle 201 is movable. On the other hand, when user 203 presses the "Cannot drive" button, server 101 receives information that, according to user 203's judgment, vehicle 201 is immobile.

[0080] The messages directed to user 203 are not limited to the examples above. For example, messages with different wording may be used. Furthermore, messages are not limited to being displayed on the screen; they may also be delivered using other GUIs or output via voice, etc.

[0081] Furthermore, user 203's decision-making is not limited to GUI input methods such as buttons. For example, user 203 could call a call center and communicate their decision, and the operator who receives the call could input user 203's decision. This type of input is also effective in disasters where mobile phone lines remain operational, such as when heavy rainfall is concentrated in a relatively small area (where other areas are less affected by the disaster, and call centers and communication infrastructure are not significantly impacted).

[0082] Hereinafter, the decision of whether or not movement is permitted by user 203 will be referred to as "self-declaration." As described above, self-declaration is entered by user 203 through operations on the information processing terminal 204 or the in-vehicle device 102, etc. In contrast, the decision of whether or not movement is permitted may be made, for example, by an employee of a company providing a shared service at a call center, or by server 101 analyzing the information.

[0083] If the server determines that vehicle 201 is movable (YES in step S50), the server proceeds to step S70. On the other hand, if the server determines that vehicle 201 is immovable (NO in step S50), the server proceeds to step S60.

[0084] In "disaster mode," the processing differs depending on the mobility status of vehicle 201, for example, as follows:

[0085] In step S60, server 101 changes the return location. For example, the initial return location is station 200 from which the vehicle departed. However, if it is determined that vehicle 201 is unable to move due to a disaster or other reason (NO in step S50), server 101 changes the return location from station 200 from which the vehicle departed to the nearest parking lot or similar location.

[0086] In the following steps, the return location that is changed from the initially set return location in step S60 will be referred to as the "changed location". The changed location does not have to be the nearest parking lot, etc. For example, if the vehicle 201 is completely immobile, the server 101 may set that location, i.e., the current location (the position where the vehicle 201 is immobile and stopped), as the changed location.

[0087] If vehicle 201 is immobile due to a disaster or other reason, user 203 will often find it difficult to return vehicle 201 to the return location. Furthermore, disasters may occur at the return location. In this case as well, user 203 will find it difficult to return vehicle 201 to the return location. Therefore, if the initial return location (before the change) remains unchanged, user 203 may attempt to return the vehicle to the initial location despite the disaster. To address this, server 101 changes the return location to, for example, an area with less concern about disasters, or a parking lot where vehicle 201 needs to be moved less frequently.

[0088] This approach prevents user 203 from unnecessarily moving vehicle 201 for return purposes, or from approaching areas affected by disasters, thereby reducing the risk of user 203 being endangered by disasters. Furthermore, since the return location can be changed without communication via telephone or other means, it helps prevent congestion on mobile phone lines.

[0089] In step S70, server 101 sets the designated location. Step S70 occurs when special circumstances have arisen (YES in step S20) and vehicle 201 is movable (YES in step S50). Therefore, it is desirable that vehicle 201 be returned to a parking lot or similar location managed by the company providing the sharing service, where there is little risk of disaster or other dangers.

[0090] Hereinafter, in the event of special circumstances, the parking lot or other location where user 203 is instructed to return vehicle 201 will be referred to as the "designated location." The designated location may be set by, for example, an employee of the company providing the sharing service.

[0091] The designated location is the nearest parking lot from the current location, or a parking lot in an area free from the risk of disaster, etc., and closest to the initially set return location. Alternatively, the designated location may be the initially set return location, i.e., the departure station 200. For example, if it is confirmed that the departure station 200 is in an area largely unaffected by disasters, the designated location may remain the departure station 200, i.e., the initial setting may be maintained.

[0092] As described above, once the overall process is complete, if special circumstances arise, i.e., if disaster mode is activated, user 203 will be notified first. After the notification, the initial return location will be set to a designated location or a changed location, depending on the mobility status of vehicle 201.

[0093] Figure 8 shows a second example of the overall processing. Hereafter, processes similar to those in Figure 3 will be denoted by the same reference numerals and their explanations will be omitted. In the first example, the processing entity is consistently server 101, whereas in the second example, the processing entity differs depending on the process.

[0094] For example, step S50 may be performed on the in-vehicle device 102, i.e., the information processing device on the vehicle 201 side.

[0095] In step S50, the in-vehicle unit 102 determines whether the vehicle 201 is mobile or not. Specifically, the in-vehicle unit 102 may obtain data from sensors on the vehicle 201 or from an external device 205 (which may be obtained from a server 101, etc.) to determine if the vehicle 201 is malfunctioning or otherwise inoperable.

[0096] Alternatively, after step S50 is performed by the in-vehicle device 102, the decision result may be sent to the server 101. On the other hand, step S50 may be divided among the in-vehicle device 102, etc., to collect data from the vehicle 201 and send it to the server 101, and the server 101 to make a decision based on the transmitted data.

[0097] Thus, since the vehicle 201 has sensors and other equipment on the vehicle 201, if the sensor data and other information can be processed without sending it to the server 101, the processing load on the server 101 can be reduced.

[0098] Note that the process executed by the in-vehicle device 102 is not limited to step S50; other processes may also be performed.

[0099] However, in the vehicle management system 100, if the overall processing is performed by multiple information processing devices, the results of the processing, or data, etc., may be mutually transmitted and received for information sharing.

[0100] Furthermore, each process may be executed in a distributed, redundant, or parallel manner. In addition, decisions may be made using different data or criteria on multiple information processing devices, with the final decision made by majority vote.

[0101] [Regarding special circumstances] Special circumstances are any circumstances that affect the movement or return of vehicle 201.

[0102] Specifically, special circumstances include natural disasters, social upheavals, weather events, fires, accidents, or traffic conditions. For example, what constitutes a special circumstance is predetermined. Furthermore, if multiple types of special circumstances are defined, the data used to determine whether or not a special circumstance has occurred, the source of that data, the criteria for determining whether or not a special circumstance has occurred, or the method of determination are also predetermined.

[0103] [Examples of circumstances that may be considered special] Figure 9 shows examples of what constitutes a special circumstance. For example, if at least one of the following is determined: the return location (represented as the "departure station" in the figure) or the current location (represented as the "vehicle" in the figure), is within an area where a disaster has occurred (represented as being in a "disaster area" in the figure), then a special circumstance is determined to exist, and the vehicle enters "disaster mode."

[0104] Whether or not special circumstances exist is not limited to the current location. For example, the return location of vehicle 201 (including cases where a location other than the departure station 200 is set) or the route between the current location and the return location (hereinafter simply referred to as "the route") may also be the subject of the determination. In such cases, if special circumstances exist for at least one of the return location, current location, and route, it is determined that special circumstances exist (YES in step S20).

[0105] The route is determined, for example, by searching for a route from the current location to the destination (return location) using a car navigation system or similar. Furthermore, the route only needs to include locations that could potentially be traveled on the way to the return location; if multiple routes are possible, all of them may be considered.

[0106] Figure 10 shows an example where the current location, return location, and route are the factors to be considered. When the route is added to the factors to be considered as shown in Figure 9, if the return location, current location, and route are not all within the area where a disaster has occurred (in the figure, this means they are not within the "disaster area"), then it is determined that no special circumstances have occurred, and the case will not enter "disaster mode".

[0107] On the other hand, "disaster mode" is also considered to be activated when only the route is within an area affected by a disaster, when both the route and the current location are within an area affected by a disaster, or when both the route and the return location are within an area affected by a disaster.

[0108] Furthermore, the determination of special circumstances does not have to be based solely on the current location, return location, and route (hereinafter collectively referred to as "Region 1"). For example, neighboring areas of Region 1 (hereinafter referred to as "Region 2") may also be included in the determination. Neighboring areas include, for example, adjacent areas or areas within a certain distance.

[0109] For example, in the case of large-scale disasters such as typhoons or earthquakes, the impact often extends to a wide area. Furthermore, in areas particularly severely affected by the disaster, such as the epicenter, equipment failures are more likely, and it may be impossible to obtain relevant data. Therefore, the first region may be determined based on the second region, which is a neighboring area.

[0110] Specifically, if it can be presumed that special circumstances have occurred in the first region based on the data of the second region, if special circumstances have occurred in the first region within a certain period, or if there is a high probability that special circumstances will occur in the first region based on the judgment of operators, etc., then it may be determined that the first region is located where special circumstances have occurred.

[0111] Thus, by utilizing not only data on the specific circumstances of the target region, but also data on neighboring regions such as the second region, a more flexible approach can be taken.

[0112] [Variations of the criteria for determining special circumstances and the feasibility of travel] It is preferable not to determine whether or not special circumstances have arisen, and whether or not special circumstances have arisen at any of the locations among the current location, the return location, and the route, based solely on information such as contact from user 203 (step S20).

[0113] Similarly, it is desirable that the determination of whether a vehicle is mobile is not based solely on self-reported information (Step S50). For example, it is desirable that the determination of whether a vehicle is mobile be based on multiple determinations, including self-reported information, determinations by operators at the call center, and determinations based on circumstances data. Specifically, this could involve a majority vote based on multiple determinations, or assigning priority or weight to each determination.

[0114] In addition, the feasibility of movement can sometimes be determined from sensor data, for example, if vehicle 201 is submerged in water or malfunctions due to a disaster. Thus, if vehicle 201 is unable to move under its own power due to a malfunction or if it is estimated that it would be highly dangerous for user 203 to move vehicle 201, it is desirable to determine that it is immobile (NO in step S50).

[0115] For example, to determine whether special circumstances exist, server 101 determines that special circumstances exist if, in the area where user 203 has made contact, other administrative agencies such as the Japan Meteorological Agency have also issued information indicating similar circumstances to those reported by user 203 (YES in step S20). In this way, server 101 determines that special circumstances exist not only when information is consistent across multiple sources, but also when information is included from sources that are considered highly reliable, such as administrative agencies.

[0116] Similarly, the determination of whether a vehicle is mobile is made, for example, based on self-reporting and data from sensors installed on vehicle 201. If a malfunction or other issue is detected, server 101 determines that a special circumstance has occurred (YES in step S20).

[0117] [Example of remote control] In particular, if special circumstances arise (YES in step S20) and vehicle 201 is immobile (NO in step S50), it is desirable that server 101 be able to remotely control vehicle 201. For example, if vehicle 201 is immobile, the destination may be a general road or similar location, rather than a parking lot. In such cases, it is desirable that server 101 be able to remotely control, for example, opening and closing the doors of vehicle 201.

[0118] In the event of a disaster or other emergency, parking on the roadway may be permitted as an emergency measure. However, if vehicle 201 is not moved immediately to ensure a clear path for emergency vehicles, it may become an obstacle. Therefore, being able to remotely open and close the doors of vehicle 201, allowing someone nearby to operate them immediately, would enable a swift response to emergencies.

[0119] Furthermore, through remote operation, server 101 may terminate the service with vehicle 201 unlocked (i.e., not locked). Because the vehicle 201's lock can be operated remotely, even if the service is terminated with vehicle 201 unlocked, the vehicle 201 can be locked without an administrator having to go to its current location, enabling efficient management.

[0120] Furthermore, remote control is defined as a system where the operator or the information processing device that performs the processing is located away from the vehicle 201 and operates via communication, etc., without physical contact with the vehicle 201. In other words, it is preferable that the server 101 be controlled remotely via communication rather than being controlled by a wired connection to the vehicle 201.

[0121] [Example of Functional Configuration] Figure 11 shows an example of a functional configuration. For example, the server 101 includes a determination unit 101F1, a notification unit 101F2, and a setting unit 101F3, etc. However, each functional unit may be provided by an information processing device other than the server 101 in the vehicle management system.

[0122] The determination unit 101F1 performs a determination procedure to determine whether the current location, return location, or route of the vehicle 201 subject to sharing or lending is in a location where special circumstances have occurred. For example, the determination unit 101F1 is implemented by the CPU 101H1 or the like.

[0123] If the notification unit 101F2 determines that the current location, return location, or route is in a location where special circumstances have occurred, it performs a notification procedure to notify the vehicle 201 that special circumstances have occurred. For example, the notification unit 101F2 is implemented by the CPU 101H1 or the like.

[0124] The setting unit 101F3 performs a setting procedure to set the return location according to the mobility status of the vehicle 201. For example, the setting unit 101F3 is implemented by the CPU 101H1 or the like.

[0125] With the above configuration, in the event of a disaster or other special circumstances, the vehicle 201 can be notified to user 203 who is using the vehicle. Furthermore, even under circumstances such as a disaster, settings such as changing the return location can be made to reduce the likelihood of forcing user 203 to make an unreasonable return, thereby providing a service that can adapt to a variety of changes in usage.

[0126] [Differentiation] In the example above, we explained using two modes: "Normal Mode" and "Disaster Mode," but the modes are not limited to these. For example, there may be three or more modes. Also, the names of the modes are not limited to "Normal Mode" and "Disaster Mode"; other names are also acceptable.

[0127] [Other embodiments] Furthermore, each device does not necessarily have to be a single device. In other words, each device may be a combination of multiple devices.

[0128] The present invention may be implemented by a process for realizing the vehicle management method exemplified above, or by a program (including firmware and things equivalent to a program; hereinafter simply referred to as "program") that performs a process equivalent to the process described above.

[0129] In other words, the present invention may be implemented by a program written in a programming language or the like, which issues commands to a computer to obtain a predetermined result. The program may also be configured so that a part of the processing is executed by hardware such as an IC (integrated circuit).

[0130] A program causes the computer to perform the above-mentioned processes by having its arithmetic unit, control unit, and memory device work together. In other words, a program is loaded into main memory, issues commands to the arithmetic unit to perform calculations, and operates the computer.

[0131] Furthermore, the program may be provided via a computer-readable storage medium or via a telecommunications line such as a network.

[0132] The present invention may be implemented in a system composed of multiple devices. That is, an information processing system consisting of multiple computers may execute the above-described processes in a redundant, parallel, distributed, or combination thereof. Therefore, the present invention may be implemented in devices other than those described above, and in systems other than those described above.

[0133] The processing in this invention (including data storage, or a part of the processing) may be performed on an information processing device installed overseas.

[0134] It should be noted that the present invention is not limited to the embodiments exemplified above. Therefore, the present invention can be modified by adding or changing components without departing from the technical spirit. Thus, all technical matters included in the technical concept described in the claims are covered by the present invention. The embodiments exemplified above are specific examples that are suitable for implementation. Furthermore, those skilled in the art can implement various modifications from the disclosed content, and such modifications are included in the technical scope described in the claims. [Explanation of Symbols]

[0135] 100: Vehicle Management System 101: Server 101F1: Judgment section 101F2:Notification section 101F3: Setting section 101H1: CPU 101H2: Storage device 101H3: Input device 101H4: Output device 101H5 :Communication equipment 102: In-vehicle device 102H1: CPU 102H2: Storage device 102H3: Input device 102H4: Output device 102H5 :Communication device 102H6: Position sensor 200: Station 201: Vehicle 202:Payment machine 203: User 204: Information Processing Terminal 204H1: CPU 204H2 :Storage device 204H3: Input device 204H4: Output device 204H5 :Communication equipment 204H6: Position Sensor 205: External device 300: Message Box 301: Map display 302: Pop-up display 303: Input button

Claims

1. A determination unit that determines whether the current location of a vehicle to be shared or leased, the return location, or the route between the current location and the return location is in a location where special circumstances exist, When it is determined that the current location, the return location, or the route is in a location where the special circumstances are occurring, a notification unit provides a notification indicating that the vehicle is in a special situation. A setting unit sets the return location according to the mobility status of the vehicle. A vehicle management system equipped with the following features.

2. The aforementioned setting unit is, If the vehicle is able to move to the return location, the return location shall be designated as a predetermined location. If the vehicle is unable to move to the aforementioned return location, the aforementioned return location shall be changed to a different location. The vehicle management device according to claim 1.

3. The aforementioned special circumstances are, This includes natural disasters, social upheavals, natural calamities, weather, fires, accidents, or traffic conditions. The vehicle management device according to claim 1.

4. The data indicating the current location, the return location, or the special circumstances along the route is acquired from an external device or sensor. The vehicle management device according to claim 1.

5. The aforementioned setting unit is, If multiple of the following determinations regarding the feasibility of movement—the determination made by the user using the vehicle, the determination made by the operator at the call center, and the determination made based on the circumstances data—conclude that the vehicle is not movable, then it is determined that the vehicle is not able to move to the return location. The vehicle management device according to claim 4.

6. If the vehicle is unable to move to the return location, Controlling the doors of the vehicle, or the operation of the vehicle, from a remote location away from the vehicle. The vehicle management device according to claim 1.

7. The current location is, The location is identified based on location data obtained from an in-vehicle device installed in the vehicle, or from an information processing terminal owned by a user of the vehicle. The aforementioned return location is, The starting point where the vehicle is put into use, or the declared location declared by the user. The aforementioned route is This is a location that the vehicle may pass through in order to return it from the current location to the return location, and the route from the current location to the return location is searched and identified. The unit that makes the determination said, The data indicating the special circumstances in the current location, the return location, or the route is acquired for the first region including the current location, the return location, or the route, or for the second region which is a neighboring region of the first region. Based on the aforementioned circumstances data, if the aforementioned special circumstances have occurred in the first region, if the aforementioned special circumstances have occurred in the first region within a certain period of time, or if there is a high probability that the aforementioned special circumstances will occur in the first region, then it is determined that the current location, the return location, or the route is located in a place where the aforementioned special circumstances have occurred. The aforementioned notification unit, The in-vehicle unit or the information processing terminal displays a message indicating that it is in disaster mode, and notifies the user. The aforementioned setting unit is, If, due to the aforementioned special circumstances, the vehicle or the user determines that the vehicle is unable to move under its own power, or that moving the vehicle would be extremely dangerous, then it is determined that the vehicle cannot be moved to the return location. The vehicle management device according to claim 1.

8. A vehicle management system having a vehicle management device and an in-vehicle device connected to the vehicle management device, A determination unit that determines whether the current location of a vehicle to be shared or leased, the return location, or the route between the current location and the return location is in a location where special circumstances exist, When it is determined that the current location, the return location, or the route is in a location where the special circumstances are occurring, a notification unit provides a notification indicating that the vehicle is in a special situation. A setting unit sets the return location according to the mobility status of the vehicle. A vehicle management system equipped with the following features.

9. A vehicle management method performed by a vehicle management device, The vehicle management device includes a determination procedure for determining whether the current location, return location, or the route between the current location and the return location of a vehicle subject to sharing or lending is in a location where special circumstances exist. A notification procedure in which the vehicle management device determines that the current location, the return location, or the route is at a location where the special circumstances are occurring, and provides a notification indicating that the vehicle is experiencing the special circumstances, The vehicle management device sets the return location according to the vehicle's mobility status, and A vehicle management method that includes this.

10. A program for causing a computer to execute the vehicle management method described in claim 9.

Images