JP7635733B2 - Vehicle management server - Google Patents

Description

This disclosure relates to a vehicle management server that manages the maintenance of vehicle parts.

Patent Document 1 discloses a vehicle driving assistance system for electric vehicles that automatically searches for battery stations from the latest map information, selects the nearest suitable battery station by the driver, provides guidance using a recalculated navigation system, obtains information such as whether or not the vehicle needs inspection, payment methods and services, and inspects the vehicle and transfers a fully charged battery at an appropriate battery station on the road before driving again, all of which function in a series of linked functions.

JP 2010-025910 A

Vehicles are equipped with parts that require maintenance, either periodically or due to various circumstances. Maintenance is usually performed at the discretion of the vehicle owner. In response to this, systems that notify the vehicle owner when maintenance is required have been devised. However, simply being notified of the time for maintenance leaves the vehicle owner with the hassle of arranging the date and time of the maintenance, arranging the shop where the maintenance is to be performed, and completing the procedures for booking the maintenance.

The technology disclosed in Patent Document 1 discloses that vehicle inspections of electric vehicles are conducted in conjunction with charging at a battery station and transferring batteries. This allows maintenance to be carried out by effectively utilizing the time spent charging and transferring batteries.

On the other hand, in addition to charging electric vehicles and transferring batteries, situations can be expected in which general vehicles are parked for long periods of time. It would be worth considering making effective use of such long-term parked time for carrying out maintenance.

In view of the above problems, one objective of the present disclosure is to provide technology that can reduce the inconvenience to vehicle owners when performing maintenance on vehicle parts. Another objective of the present disclosure is to provide technology that can perform maintenance that makes effective use of time.

This disclosure relates to a vehicle management server that manages the maintenance of vehicle parts.

The vehicle management server according to the present disclosure is configured to execute the following processes: acquiring the usage status of the parts; acquiring a usage schedule of the vehicle; extracting parts requiring maintenance based on the usage status; and, when the parts requiring maintenance have been extracted and the usage schedule indicates that the vehicle will be parked for a long period of time or longer, reserving or proposing a maintenance service according to the parking location and time period of the long-term parking period.

According to the present disclosure, parts to be maintained are extracted based on information on the usage status of parts obtained from the vehicle. Then, when parts to be maintained have been extracted and the vehicle usage schedule indicates that the vehicle will be parked for a long period of time, a reservation or proposal for a maintenance service is made according to the parking location and time period of the planned long-term parking.

This makes it possible to match long-term vehicle parking plans with maintenance of vehicle parts. This in turn reduces the inconvenience for users regarding the implementation of maintenance, such as coordinating the date and time of maintenance and the store where the maintenance will be performed, and the procedures for booking the maintenance. In addition, since the maintenance is performed while the vehicle is parked, users can make effective use of their time.

2 is a conceptual diagram illustrating a maintenance reservation function provided by the vehicle management server according to the embodiment. FIG. 10 is a flowchart showing a process according to a first embodiment of a maintenance reservation function. 13 is a flowchart showing a process according to a second embodiment of a maintenance reservation function. 13 is a flowchart showing a process according to a third embodiment of a maintenance reservation function.

Below, the embodiments of the present disclosure will be described with reference to the drawings. However, when the numbers, quantities, amounts, ranges, etc. of each element are mentioned in the embodiments shown below, the idea of the present disclosure is not limited to the mentioned numbers unless otherwise specified or the number is clearly specified in principle. Furthermore, the configurations, etc. described in the embodiments shown below are not necessarily essential to the idea of the present disclosure unless otherwise specified or the number is clearly specified in principle. In addition, the same reference numerals are used for the same or corresponding parts in each drawing, and duplicate explanations are appropriately simplified or omitted.

1. Maintenance reservation function The vehicle management server according to this embodiment manages the maintenance of vehicle parts. In particular, the vehicle management server according to this embodiment provides a reservation function for the maintenance of vehicle parts. The maintenance reservation function provided by the vehicle management server 10 according to this embodiment will be described below with reference to FIG. 1.

The vehicle management server 10 according to this embodiment is configured to be able to transmit information to and from the vehicle 1 that is the object of management. For example, the vehicle 1 performs wireless communication (e.g., cellular communication) with a base station installed in the vicinity using an on-board communication device, and the vehicle management server 10 forms a communication network that communicates with the base station via the Internet. The vehicle management server 10 may be configured to manage multiple vehicles 1. In this case, the vehicle management server 10 is configured to be able to transmit information to and from each of the multiple vehicles 1.

The vehicle 1 transmits information on the usage status of parts that require maintenance periodically or for various reasons to the vehicle management server 10. Examples of parts that require maintenance periodically or for various reasons include tires, brake pads, batteries, spark plugs, windshield wipers, and various consumables (engine oil, coolant, washer fluid, etc.). The information on the usage status of parts includes information that serves as an indicator for determining whether or not maintenance is required for each part. Examples include the date of the last maintenance, the period since the last maintenance, tire pressure, mileage with the current parts, battery voltage, and the amount of use or remaining amount of various consumables. These may be provided for each part. The vehicle 1 may also be equipped with a sensor for detecting the information on the usage status of parts.

Vehicle 1 also transmits the usage schedule of vehicle 1 to vehicle management server 10. The usage schedule of vehicle 1 includes information on the usage time period and destination for the planned use of vehicle 1 (commuting, shopping, pick-up and drop-off, etc.). Here, the plan for using vehicle 1 may be a periodic schedule (daily or weekly schedule, etc.). Furthermore, the usage schedule of vehicle 1 may include information on the route to the destination.

The usage schedule of vehicle 1 is registered by a user (typically the owner of vehicle 1). For example, the user registers the usage schedule by operating a terminal (e.g., a car navigation device) in vehicle 1. Alternatively, the user registers the usage schedule by operating his/her own user terminal (which may be a dedicated terminal or a general-purpose terminal such as a smartphone with a specified application installed). In this case, the usage schedule of vehicle 1 may be configured to be transmitted directly from the user terminal to vehicle management server 10. For example, the user terminal is connected to vehicle management server 10 via the Internet.

The usage schedule of vehicle 1 may be registered for immediately preceding events. For example, when vehicle 1 is parked in a parking lot, the estimated parking time in that parking lot may be registered as the usage schedule.

The vehicle management server 10 is typically a computer that includes a memory and a processor. In this case, the memory is coupled to the processor and stores a number of executable instructions provided by a program, as well as various data required to execute the processes. The processor operates according to the instructions to execute various processes based on the data stored in the memory. Information acquired by the vehicle management server 10 is stored as data in the memory.

The vehicle management server 10 executes a process (hereinafter also referred to as a "target part extraction process") to extract parts requiring maintenance (hereinafter also referred to as "maintenance target parts") based on information on the part usage status acquired from the vehicle 1. Examples of the target part extraction process include processes such as extracting parts requiring maintenance by comparing with data on vehicles that have previously broken down, extracting parts requiring maintenance because the time since the last maintenance is approaching or has passed the recommended maintenance period for the parts, extracting tires as parts requiring maintenance because the tire pressure is below the recommended value, and extracting a specific consumable as a part requiring maintenance because the remaining amount of the specific consumable is below a predetermined value. When a part requiring maintenance has been extracted, the vehicle management server 10 may notify the vehicle 1 or the user that there is a part requiring maintenance.

Then, when the parts to be maintained are extracted and the vehicle 1 is scheduled to be parked for a long period of time or more in the usage schedule of the vehicle 1, the vehicle management server 10 executes a process for reserving or proposing a maintenance service according to the parking location and time period in the long-term parking plan (hereinafter, also referred to as a "reservation proposal process"). Here, the predetermined time may be suitably determined according to the environment in which the vehicle management server 10 according to this embodiment is applied. For example, it may be considered to be the time generally required for maintenance. In particular, a different time may be determined according to the extracted parts to be maintained. Note that the vehicle management server 10 may be configured to execute a process for accepting parts for which maintenance is desired to be performed among the extracted parts to be maintained. In this case, a reservation for a maintenance service is not made for parts for which maintenance is not desired. By configuring in this manner, it is possible to prevent a reservation for a maintenance service from being made against the user's will. In turn, it is possible to improve usability.

When executing the reservation proposal process, the vehicle management server 10 obtains the availability of maintenance services from the business 2 that will provide the maintenance service. Examples of the business 2 include dealers, service factories, and vehicle repair shops. In the reservation proposal process, the vehicle management server 10 then selects a business 2 that can perform maintenance at the parking location and time period in the planned long-term parking, and makes a reservation for the maintenance service by specifying the parking location and time period. The reservation for the maintenance service is realized, for example, by communicating with the reservation management server of the business 2.

The business operator 2 performs the maintenance service according to the reservation made by the vehicle management server 10, so that the vehicle 1 can receive maintenance of the parts to be maintained while parked. Here, the parking location for the planned long-term parking is typically a parking lot 3 located at a different location from the business operator 2. Examples of parking lots 3 include parking lots at shopping locations, parking lots at restaurants, and parking lots at the company where the vehicle is employed. For this reason, the business operator 2 typically needs to dispatch workers when performing the maintenance service. Therefore, it is desirable for the vehicle management server 10 to make reservations for the maintenance service while taking into consideration the dispatch of such workers. For example, the reservation destination may be limited to businesses 2 whose parking lots 3 are included in the service provision area for on-site maintenance, and availability may be checked taking into consideration the time required for dispatch.

However, it is also conceivable that the parking location for long-term parking will be the business operator 2. For example, there may be a case where the vehicle 1 is an electric vehicle and charging is planned to be performed at a power supply facility installed at a dealer. In this case, there is no need to consider dispatching workers.

After making a reservation for a maintenance service, the vehicle management server 10 notifies the vehicle 1 or the user of the details of the reservation.

In addition, the vehicle management server 10 may be configured to notify the vehicle 1 or the user of reservation guidance information (e.g., store guidance and reservation time guidance) as a maintenance service proposal in the reservation proposal process, and to execute a process to confirm the acceptance of the reservation. Furthermore, the vehicle management server 10 may search for events, playgrounds, cafes, etc. where the user can kill time near the parking location where the maintenance is to be performed, and notify the user of this information as guidance information. When implementing a maintenance service proposal in this way, the vehicle management server 10 makes a reservation for the maintenance service in response to the reservation being accepted. In particular, the reservation guidance information may include information about multiple businesses 2 that are candidates for reserving the maintenance service. The server may be configured to accept the selection of a business 2 that accepts (desires) the reservation from among the multiple businesses 2. By configuring in this way, it is possible to prevent a maintenance service reservation from being made against the user's will. In turn, it is possible to improve usability.

Furthermore, even if there is no long-term parking planned in the usage schedule of vehicle 1 and the reservation proposal process is not executed, the vehicle management server 10 may execute a process (hereinafter also referred to as "schedule proposal process") to propose including a long-term parking plan in the usage schedule in response to the extraction of a part to be maintained in the target part extraction process. Here, the proposed long-term parking plan is given based on learning about the past usage status of vehicle 1. For example, it may learn that there is a regular weekly plan (lessons, work, shopping, etc.) and propose that it be included in the usage schedule as a long-term parking plan. Note that the usage status of vehicle 1 may be configured to be acquired sequentially or periodically from vehicle 1, or may be configured to be acquired by referring to the current or past usage schedule of vehicle 1.

When it is agreed that long-term parking plans can be included in the usage schedule and the usage schedule is registered, the vehicle management server 10 will make a reservation for the maintenance service.

2. Examples Hereinafter, several examples of the maintenance reservation function realized by the vehicle management server 10 will be described.

2-1. First Example A first example of the maintenance reservation function will be described with reference to Fig. 2. Fig. 2 is a flowchart showing the processing according to the first example. The first example assumes a case where some parts of the vehicle 1 have expired maintenance dates or where the maintenance deadline is approaching.

In step S100, parts that require maintenance are extracted. This is performed by executing a target part extraction process in the vehicle management server 10. In the following explanation, it is assumed that at least one part that requires maintenance is extracted in step S100. Note that if no part that requires maintenance is extracted in step S100, the process ends without executing a reservation proposal process or a schedule proposal process.

After step S100, processing proceeds to step S110.

In step S110, a selection of parts to be maintained from the parts to be maintained extracted in step S100 is accepted. For example, the user selects the parts to be maintained that are the subject of the reservation proposal process by operating the terminal of vehicle 1 or the user terminal. Here, the user may be notified of the time and cost required for maintenance for each of the parts to be maintained.

After step S110, if there is no plan for long-term parking in the usage schedule of vehicle 1 (step S120; No), it is suggested that a plan for long-term parking be included in the usage schedule (step S130). This is performed by executing a schedule suggestion process in the vehicle management server 10. After step S130, the processing related to the first embodiment ends.

After step S110, if the usage schedule for vehicle 1 includes a plan for long-term parking (step S120; Yes), processing proceeds to step S140.

In step S140, a business operator 2 that can perform on-site maintenance for the parking location and time period planned for long-term parking is extracted.

After step S140, processing proceeds to step S150.

In step S150, the cheapest provider 2 is selected from the providers 2 extracted in step S140, and a reservation for the maintenance service is made. The user is also notified that the reservation has been completed. The processes related to steps S140 and S150 are performed by the vehicle management server 10 executing a reservation proposal process.

After step S150, processing proceeds to step S160.

In step S160, the on-site maintenance is carried out by the reserved business operator 2. At this point, the user may be notified of the time when the on-site maintenance will be completed. After step S160, the processing related to the first embodiment ends.

3-2. Second Example Next, a second example of the maintenance reservation function will be described with reference to Fig. 3. Fig. 3 is a flowchart showing the processing according to the second example. The second example assumes a case where parts that are subject to maintenance have been extracted by executing the target part extraction processing, there is no plan for long-term parking in the current usage schedule, and a reservation for a maintenance service has not yet been made.

In step S200, the vehicle 1 is parked in a parking lot 3 that is subject to maintenance services from one of the businesses 2.

After step S200, processing proceeds to step S210.

In step S210, the estimated parking time of vehicle 1 in parking lot 3 is registered by the user as a usage schedule.

After step S210, if the estimated parking time indicates that vehicle 1 is not parked for a long period in parking lot 3 (step S220; No), the reservation proposal process is not executed and the process according to the second embodiment ends.

After step S210, if the estimated parking time indicates that vehicle 1 is parked in parking lot 3 for a long period of time (step S220; Yes), processing proceeds to step S230.

In step S230, a business operator 2 capable of on-site maintenance at the parking lot 3 where the vehicle 1 will be parked during the estimated parking time is extracted.

After step S230, the process executes the processes related to steps S240 and S250. Here, the processes related to steps S240 and S250 are equivalent to the processes related to steps S150 and S160. After step S250, the process related to the second embodiment ends.

3-3. Third Example Next, a third example of the maintenance reservation function will be described with reference to Fig. 4. Fig. 4 is a flowchart showing the processing according to the third example. The third example assumes a case in which the vehicle 1 is an electric vehicle and is unable to reach a destination set in a navigation system or the like with the current remaining battery charge.

In step S300, the destination is set in a navigation system or the like.

After step S300, processing proceeds to step S310.

In step S310, the vehicle management server 10 calculates the remaining battery power required to reach the destination. This may be performed in the vehicle 1 or in the vehicle management server 10.

After step S310, if the current remaining battery level is greater than the required remaining battery level calculated in step S310 (step S320; No), the processing for the third embodiment ends.

After step S310, if the current battery remaining amount is less than the required battery remaining amount calculated in step S310 (step S320; Yes), processing proceeds to step S330.

In step S330, parts that require maintenance are extracted. This is performed by executing a target part extraction process in the vehicle management server 10. In the following explanation, it is assumed that at least one part that requires maintenance is extracted in step S330.

After step S330, processing proceeds to step S340.

In step S340, the vehicle management server 10 extracts businesses 2 that can perform maintenance on the parts to be maintained that were extracted in step S330.

Next, in step S350, the vehicle management server 10 further extracts businesses 2 that have power supply equipment from the businesses 2 extracted in step S340.

Next, in step S360, the vehicle management server 10 extracts from the businesses 2 extracted in step S350, businesses 2 within a predetermined range (near the route to the destination) of a point on the route to the destination set in step S300. Here, the route to the destination may be given by the usage schedule, or may be obtained by communication with the vehicle 1.

The vehicle management server 10 notifies the user of the guidance information of the business 2 extracted in step S360. Furthermore, the vehicle management server 10 accepts the user's preference regarding the business 2 extracted in step S360.

After step S360, if the operator 2 desired by the user is not among the operators 2 extracted in step S360 (step S370; No), the processing related to the third embodiment ends.

After step S360, if the operator 2 desired by the user is among the operators 2 extracted in step S360 (step S370; Yes), processing proceeds to step S380.

In step S380, the vehicle management server 10 notifies the user of the available reservation times (multiple selections may be possible) with the desired business operator 2, and confirms acceptance of the reservation. Here, the expected arrival time at the business operator 2 may also be highlighted.

After the user accepts the reservation, the reservation for maintenance and charging is made at the selected reservation available time (step S390). This allows the user to enjoy maintenance while charging at the desired business operator 2. Ultimately, charging time can be used effectively. After step S390, the processing related to the third embodiment ends.

3. Effects As described above, according to this embodiment, parts to be maintained are extracted based on information on the usage status of parts acquired from the vehicle 1. Then, in response to the fact that parts to be maintained have been extracted and that the usage schedule of the vehicle 1 includes a plan for long-term parking, a reservation for a maintenance service is made according to the parking location and time period of the planned long-term parking.

This makes it possible to match the long-term parking schedule of vehicle 1 with the maintenance of vehicle 1's parts. In turn, it makes it possible to reduce the inconvenience to the user regarding the implementation of maintenance, such as coordinating the date and time of the maintenance and the store where the maintenance will be performed, and the procedures for booking the maintenance. In addition, since the maintenance is performed while vehicle 1 is parked, time can be used effectively.

1 Vehicle 2 Business operator 3 Parking lot 10 Vehicle management server

Claims (2)

A vehicle management server that manages maintenance of vehicle parts,
A process of acquiring a usage status of the part;
A process of acquiring a usage schedule of the vehicle registered by a user ;
A process of extracting maintenance target parts that require maintenance based on the usage status;
a process of selecting a business entity capable of performing maintenance of the maintenance target part in the parking location and time period of the planned long-term parking in response to the extraction of the maintenance target part and the existence of a plan for long-term parking in which the vehicle is parked for a predetermined period of time or more in the usage schedule;
A process of making a reservation for a maintenance service for the parking location and the time period where the long-term parking is planned by the selected business operator or making a proposal to the user;
A vehicle management server configured to execute the above steps. 2. The vehicle management server according to claim 1,
In response to the extraction of the maintenance target part when the long-term parking is not scheduled in the usage schedule, a process of suggesting to the user that the long-term parking schedule be included in the usage schedule is further executed.
A vehicle management server configured as follows.

Images