Management server and computer program

Abstract

Car-sharing vehicles are provided to those who need a replacement vehicle, and users can stop using the car-sharing service once they no longer need a replacement vehicle. [Solution] The management server comprises: a replacement vehicle completion receiving means that receives replacement vehicle completion data from an insurance server which is a server related to a non-life insurance company; a vehicle data receiving means that receives vehicle data from the shared car, along with the vehicle ID and vehicle location data, indicating that the shared car has been returned to a predetermined return location after being used as a replacement vehicle; a vehicle return confirmation means that uses the vehicle location data and the replacement vehicle completion data to confirm that the vehicle related to the vehicle ID has been returned to a predetermined return location; and a temporary ID revocation means that revoks the temporary member ID and registers it in the temporary member database based on the return confirmation.

Description

Technical Field

[0001] The present invention relates to information and communication technology that enhances the convenience of replacement vehicles associated with automobile accidents for both users and business operators.

Background Art

[0002] When a private car or company car breaks down, or when a situation requiring repair occurs due to an accident, the driver of the vehicle in need of repair often still requires the vehicle immediately after the incident. In that case, another vehicle (alternative vehicle = replacement vehicle) must be prepared.

[0003] If the contract between the driver and the non-life insurance company includes terms under which a replacement vehicle is provided during the repair period, the driver (insurance policyholder) who has sent the vehicle for repair requests a replacement vehicle from the non-life insurance company. A replacement vehicle may also be provided to the accident victim when the driver is the at-fault party.

[0004] Non-life insurance companies rarely own replacement vehicles in-house. When a replacement vehicle is needed, they request a vehicle rental business operator or other operator that owns vehicles (hereinafter referred to as "replacement vehicle provider") to arrange the replacement vehicle. Based on the results of discussions with the non-life insurance company, the replacement vehicle provider provides the owned vehicle as a replacement vehicle to the insurance policyholder for a predetermined period (the vehicle repair period). The same applies to accident victims if they so desire. A common provision form for replacement vehicle providers is to deliver the vehicle to a designated location such as the home of the insurance policyholder or the home of the accident victim, and collect the vehicle when the repair period ends.

[0005] This will be described in detail with reference to Figure 1. Italicized numbers in parentheses in the figure indicate the order of procedures. In the following description, the driver is referred to as "insurance policyholder" for clarity in explaining the relationship with the non-life insurance company. However, the situation where the insurance policyholder is the driver operating the vehicle remains unchanged in the subsequent description. Assume that an accident occurs while the policyholder is riding in the insured vehicle (1).

[0006] The policyholder contacts the insurance company's call center about the accident using a mobile device (user terminal) (2). The call center takes necessary information from the policyholder verbally and explains what to do on the spot and what procedures to follow.

[0007] If the vehicle requires repair, the call center will contact the vehicle repair shop and request the repairs (3). At this time, they will obtain an estimated repair period from the vehicle repair shop. Based on that repair period, they will request a loaner vehicle from the loaner vehicle provider to arrange a loaner vehicle for the appropriate period (4). The make and model of the vehicle involved in the accident will also be provided for reference.

[0008] The replacement vehicle provider will contact the insurance policyholder to inform them of the type of vehicle and for how long they will provide it as replacement vehicle data (5), and then deliver the replacement vehicle (6). The replacement vehicle data will also be communicated to the non-life insurance company.

[0009] The following prior art examples were identified that aim to streamline the arrangement of replacement vehicles. For example, Patent Document 1 discloses a technology that facilitates understanding the operating status of vehicles and facilitating the search for the vehicle with the best conditions when determining a replacement vehicle for a vehicle in the event of an emergency.

[0010] Patent Document 2 discloses a technology for quickly arranging a replacement vehicle when a shared car involved in an accident in a car-sharing service has a subsequent reservation and the vehicle becomes unavailable to that reservation holder. [Prior art documents] [Patent Documents]

[0011] [Patent Document 1] Japanese Patent Publication No. 2003-6794 [Patent Document 2] Patent No. 6841729 [Overview of the Initiative] [Problems that the invention aims to solve]

[0012] Figure 2 illustrates the problems faced by the non-life insurance company, the policyholder (and the accident victim), and the replacement vehicle provider.

[0013] (Problem with matching replacement vehicles) For non-life insurance companies, matching the vehicles available from replacement vehicle providers with the vehicles requested by policyholders was a time-consuming process. For insurance policyholders, this meant that it took time for a replacement vehicle to be provided, or for the desired vehicle model to be available, forcing them to compromise on the type of vehicle they wanted.

[0014] (The problem of providing replacement vehicles during unnecessary hours) Insurance policyholders don't necessarily need a replacement vehicle for the entire duration of their vehicle's recovery. In other words, there are often periods when a policyholder doesn't need a replacement vehicle. For both replacement vehicle providers and non-life insurance companies, the standard service model involves providing a replacement vehicle for the entire period until the insured vehicle is returned. Their business models are not designed to accommodate periods when a replacement vehicle is not needed. This means that costs are incurred even during times when a replacement vehicle is not required, ultimately leading to higher insurance premiums.

[0015] (Administrative issues regarding insurance coverage) Insurance policyholders may terminate their insurance coverage while receiving a replacement vehicle. This is because if the cost of the replacement vehicle is covered by the insurance policy, the insurance rating will be revised, resulting in disadvantages such as a downgrade in the rating or an increase in the next premium payment. Terminating insurance coverage midway also creates administrative burdens for both the non-life insurance company and the replacement vehicle provider.

[0016] (The effort involved in dispatching and retrieving replacement vehicles) As a replacement vehicle provider, we must deliver the replacement vehicle to the location requested by the insurance policyholder. When going to that location, one of the provider's employees can drive the replacement vehicle, but on the return trip, the policyholder will either use another means of transportation or ride in a different vehicle driven by another employee. When an insurance policyholder returns a replacement vehicle, the insurance company must drive the vehicle to a location convenient for the policyholder and retrieve it. As mentioned above, dispatching and retrieving replacement vehicles incurs significant labor costs for the provider of the replacement vehicle (and the cost of using another vehicle if necessary). These costs ultimately contribute to higher insurance premiums.

[0017] The above analysis of the actual situation regarding replacement vehicles reveals that replacement vehicles are a potential factor that drives up insurance premiums. In other words, there is a latent need among non-life insurance companies to suppress factors that drive up insurance premiums in order to secure new policyholders.

[0018] (Vehicle replacement providers and car-sharing businesses) Rental car companies are widely used as providers of replacement vehicles. Some rental car companies also operate car-sharing businesses in addition to their rental car business. A car-sharing business is a self-service business in which a company owns vehicles (referred to as "shared vehicles" or "shared cars") and parks them in designated parking lots (car-sharing stations), and car-sharing members go to those parking lots to use the shared cars and return them to the same parking lots.

[0019] In the car-sharing business, revenue is generated when owned vehicles are used by member users. Therefore, if a service that provides shared cars as replacement vehicles during accidents can be offered in time slots when the vehicles are not in use, the profitability of the car-sharing business will be improved. By utilizing the system of rental and return at car-sharing stations, it is expected that the aforementioned delivery driving and collection driving by replacement vehicle providers can be eliminated.

[0020] Even in Patent Document 1, Patent Document 2, or the patent search conducted to extract the aforementioned documents, no service in which a car-sharing business operator provides replacement vehicles instead of a replacement vehicle provider was found.

[0021] With reference to Figure 3, problems that may arise when assuming that a car-sharing business operator provides replacement vehicles will be described.

[0022] As a general business, car-sharing business operators make shared cars available to individual members and corporate members who have completed membership registration. On the other hand, non-life insurance companies will provide replacement vehicles required by policyholders and accident victims via the car-sharing business operator, based on a contract with the car-sharing business operator. Accordingly, preparation procedures different from the registration for individual members and corporate members are required. That is, it is necessary to prepare and complete an information processing procedure related to the "different preparation procedures" (Figure 3(a)).

[0023] Individual members in general car-sharing businesses pre-register data such as driver's license information and the payment method for car-sharing usage fees. The car-sharing business operator issues a member ID in association with the registration, whereby it is possible to execute reservation procedures for car-sharing usage from individual members who have become members, and settlement procedures for usage fees after usage is completed. However, neither the insurance policyholder nor the accident victim knows at the time of the insurance contract whether or not they will need a replacement vehicle. A replacement vehicle may be needed only if an accident occurs, and some policyholders may not need one until the insurance contract period ends. Therefore, the prerequisite for using car sharing, which is to register in advance and become a member, is lacking. Since the prerequisite must be changed, car sharing operators must decide on and prepare new methods for verifying and managing users (Figure 3(b)).

[0024] In typical car-sharing services, registered users decide on the date and time of use, complete the reservation process, and then use the service. In other words, the start and end dates of the shared car's use are predetermined. However, when insurance policyholders or accident victims use a shared car as a replacement vehicle through car-sharing, the end date of use is not fixed. This is because it is uncertain when the repairs to the vehicle involved in the accident will be completed. A lending method where the end time of use is undetermined is not anticipated in general car-sharing businesses, meaning that new management methods must be decided upon and prepared (Figure 3(c)).

[0025] In most car-sharing services, the start and end times of use are on the same day, a practice known as "same-day use." While there are instances of use exceeding 24 hours, such as for travel, even long-term use is typically limited to a few days before the vehicle is returned. Furthermore, car-sharing operators prepare an appropriate number of shared cars based on demand data derived from long-term usage. On the other hand, if we consider using shared cars as replacement vehicles in the event of an accident, the period would likely be several days at the short term, and potentially several weeks at the long term. This is a different usage pattern from previous car-sharing businesses, and there is no accumulated historical data on accident frequency, etc. Therefore, if the use of shared cars as replacement vehicles in the event of an accident begins, there is a possibility that a shortage of shared cars will occur at car-sharing stations where shared cars are deployed. Such a situation is not anticipated in general car-sharing businesses, and it means that new management methods must be decided and prepared (Figure 3(d)).

[0026] The problem that the present invention aims to solve is to provide information processing technology that can implement a special type of car-sharing business (a replacement vehicle provision business) in which the end time of use is undetermined, among the new problems mentioned above. Furthermore, since the boundaries between car-sharing businesses and car-rental businesses have become blurred due to the mutual incorporation of the best aspects of each, we will use the term "car-sharing business (or car-sharing service)" in the following explanation. [Means for solving the problem]

[0027] To address the aforementioned issues, we will provide car-sharing vehicles that can be used as replacement vehicles to those who need them, and allow them to stop using the car-sharing service once they no longer need a replacement vehicle.

[0028] (First invention) The first invention relates to a management server (car-sharing management server) for operating a car-sharing business that lends vehicles to registered member users and others, including providing replacement vehicles to policyholders of non-life insurance companies. The management server is A vehicle management database that stores reservation data for shared cars managed by the aforementioned car-sharing business operator, linked to a vehicle ID assigned to each vehicle, A means for issuing temporary member IDs to identify temporary members who can temporarily use the aforementioned shared car as a replacement vehicle, The system includes a temporary member database that stores attribute data of the temporary member linked to the aforementioned temporary member ID (see Figures 4 and 5). Furthermore, A temporary member who has obtained the aforementioned temporary member ID has used the shared car related to the reservation data as a replacement vehicle, and a replacement vehicle termination data, which is a notification that the replacement vehicle is no longer needed, is received from the insurance server, which is the server of the aforementioned non-life insurance company, by a replacement vehicle termination receiving means. A vehicle data receiving means receives vehicle data from the aforementioned shared car, along with the vehicle ID and vehicle location data, indicating that the shared car has been returned to a designated return location after being used as a replacement vehicle. A vehicle return confirmation means that uses the aforementioned vehicle location data and the aforementioned replacement vehicle completion data to confirm that the vehicle associated with the aforementioned vehicle ID has been returned to a predetermined return location, A temporary ID revocation means that revoks the temporary member ID and registers it in the temporary member database based on the return confirmation by the vehicle return confirmation means, It is equipped with (see Figure 10).

[0029] (Explanation of terms) "Car-sharing business (or operator)" refers to a car-sharing business (or operator) or rental car business (or operator) that allows users to jointly use vehicles owned by the business. Therefore, "shared car" includes not only shared cars used in car-sharing businesses, but also rental cars used in rental car businesses.

[0030] The "management server" is a computer. Therefore, it is equipped with a data receiving device as a data input device, random access memory, data storage devices, a processing unit (CPU), and a data transmission device as a data output device.

[0031] The "attribute data" of a provisional member includes data from their driver's license. This is because it is sufficient data to identify the individual, and both regular and provisional members must be qualified to drive a car. Driver's license data includes, for example, the driver's license number (12 digits) and a photograph.

[0032] "Provisional members" are managed separately from registered members. Even registered members must use a provisional member ID when using a shared car as a temporary replacement vehicle based on their damage insurance contract. In Figures 4 and 5, the "provisional member database" is illustrated as being contained within the member database, but it can also be considered an independent entity.

[0033] An "insurance policyholder" is a person who has entered into a contract with a non-life insurance company. Depending on the terms of the contract relating to the aforementioned policyholder (for example, if the contract includes provisions for providing a replacement vehicle to victims of an accident caused by the policyholder), the term may also include victims of an accident caused by the policyholder (in the diagram, these are distinguished as "policyholder (insurance policyholder)" and "victim (accident victim)"). If a person wishing to use a shared car is the policyholder (and / or accident victim), they will obtain a temporary member ID through their insurance company. The insurance company will obtain the temporary member ID issued by the car-sharing operator and provide and manage the temporary member ID to the "prospective user." The phrase "and / or" is used because the policyholder may be either the policyholder or the accident victim, or both.

[0034] Shared cars are equipped with GPS (Global Positioning System) devices, allowing them to constantly acquire their own vehicle location data. This acquired vehicle location data is then periodically (for example, every minute) transmitted to the management server. If the "vehicle location data" received by the management server's vehicle data receiving mechanism matches the location where the loaner vehicle should be returned, it can be presumed that the loaner vehicle has been returned. Since the vehicle data also includes engine on / off data and data related to locking and unlocking, combining this with engine off data and locking data can confirm that the loaner vehicle has been returned.

[0035] "Loaner vehicle completion data" refers to communication data indicating that the repair of a vehicle belonging to an insurance policyholder or accident victim has been completed, or that the repaired vehicle has been returned to the insurance policyholder or accident victim after completion of repairs. This data includes data to identify the insurance policyholder or accident victim. Because it is reasonable for non-life insurance companies to hold this "loaner vehicle completion data" due to the need for data management, it is common for management servers to receive this data from non-life insurance servers.

[0036] (action) The temporary member ID issuance system issues temporary member IDs to identify temporary members who can temporarily use a shared car as a replacement vehicle. The issued temporary member IDs are linked to the temporary member's attribute data and stored in the temporary member database. Temporary members reserve a shared car using their acquired temporary member ID. Reservation data for shared cars is stored in a vehicle management database, linked to the vehicle ID assigned to each vehicle. Temporary members then use the reserved shared car as a replacement vehicle.

[0037] Insurance policyholders can use car-sharing services by obtaining a temporary member ID, which allows them to borrow a car-sharing vehicle as a replacement vehicle. Unlike regular car-sharing, this system allows car-sharing operators to detect and manage the end of use even when a vehicle is being used as a replacement vehicle, where the end date is often unclear. Furthermore, since the temporary member ID is invalidated once the replacement vehicle use is complete, it is possible to manage usage patterns such as lending to non-members or non-payment of usage fees.

[0038] After using a shared car as a replacement vehicle, the replacement vehicle termination receiving device receives replacement vehicle termination data from the insurance server, indicating that the replacement vehicle is no longer needed. After a temporary member uses a shared car as a replacement vehicle, the vehicle data receiving device receives vehicle data from the shared car, along with the vehicle ID and vehicle location data, indicating that the car has been returned to the designated return location. The vehicle return confirmation means confirms that the vehicle associated with the vehicle ID has been returned to the designated return location based on the vehicle location data and the replacement vehicle completion data. Based on this return confirmation by the vehicle return confirmation means, the temporary ID invalidation means invalidates the temporary member ID and registers it in the temporary member database. After the invalidation of the temporary member ID is registered, the temporary member associated with the temporary member ID cannot reserve a shared car.

[0039] (Second invention) The second invention is that the rental car termination receiving means in the first invention may receive the rental car termination data, which is a notification that a rental car is no longer needed, from the communication terminal related to the temporary member, rather than from the insurance server (see Figure 15).

[0040] In other words, in a car-sharing business that lends vehicles to registered member users, it is a management server (car-sharing management server) for operating the provision of replacement vehicles to insurance policyholders of non-life insurance companies, etc. A vehicle management database that stores reservation data for shared cars managed by the aforementioned car-sharing business operator, linked to a vehicle ID assigned to each vehicle, A means for issuing temporary member IDs to identify temporary members who can temporarily use the aforementioned shared car as a replacement vehicle, The system includes a temporary member database that stores attribute data of the temporary member linked to the aforementioned temporary member ID (see Figures 4 and 5). Furthermore, A temporary member who has obtained the aforementioned temporary member ID has used a shared car related to their reservation data as a replacement vehicle, and a replacement vehicle termination data, which is a notification that the replacement vehicle is no longer needed, is received from the communication terminal of the aforementioned temporary member. A vehicle data receiving means receives vehicle data from the aforementioned shared car, along with the vehicle ID and vehicle location data, indicating that the shared car has been returned to a designated return location after being used as a replacement vehicle. A vehicle return confirmation means that uses the aforementioned vehicle location data and the aforementioned replacement vehicle completion data to confirm that the vehicle associated with the aforementioned vehicle ID has been returned to a predetermined return location, A temporary ID revocation means that revoks the temporary member ID and registers it in the temporary member database based on the return confirmation by the vehicle return confirmation means, It is equipped with (see Figure 15).

[0041] (A variation of the first or second invention) The first or second invention may be formed as follows: In other words, the system includes a temporary ID revocation transmission means that transmits a message to the communication terminal of the temporary member indicating that the temporary ID revocation means has revoked the temporary member ID.

[0042] (action) The temporary ID revocation means sends a notification to the communication terminal associated with the temporary member, informing them that the temporary ID has been revoked. The temporary member can then be aware that their temporary member ID has been revoked.

[0043] Furthermore, it is desirable that the aforementioned temporary ID invalidation notification method also sends a notification to the insurance server informing them that the temporary member ID has been invalidated. This is because it is also useful as policyholder management data for the insurance server.

[0044] (Third invention) The third invention relates to a computer program for controlling a management server (car-sharing management server) used in a car-sharing business that lends vehicles to registered member users and others, specifically for providing replacement vehicles to policyholders of non-life insurance companies. The computer program, A vehicle management data storage procedure for storing reservation data for shared cars managed by the aforementioned car-sharing business operator in a vehicle management database, linked to a vehicle ID assigned to each vehicle, and A procedure for issuing a temporary member ID to identify temporary members who can temporarily use the aforementioned shared car as a replacement vehicle, The procedure for accumulating temporary member data in the temporary member database, linked to the aforementioned temporary member ID (see Figures 4 and 5), A temporary member who has obtained the aforementioned temporary member ID has used the reserved car as a replacement vehicle, and has now received replacement vehicle termination data from the insurance server, which is the server of the aforementioned non-life insurance company, indicating that the replacement vehicle is no longer needed. A vehicle data reception procedure that receives vehicle data from the aforementioned shared car, along with the vehicle ID and vehicle location data, indicating that the shared car has been returned to the designated return location after being used as a replacement vehicle. A vehicle return confirmation procedure that uses the aforementioned vehicle location data and the aforementioned replacement vehicle completion data to confirm that the vehicle corresponding to the aforementioned vehicle ID has been returned to the designated return location, A temporary ID revocation procedure is performed to revoke the temporary member ID and register it in the aforementioned temporary member database based on the return confirmation procedure for the vehicle return. This is a computer program that is to be executed by the aforementioned management server (see Figure 10).

[0045] (Fourth invention) The fourth invention also relates to a computer program for controlling a management server (car-sharing management server) used in a car-sharing business that lends vehicles to registered member users and others, specifically for providing replacement vehicles to policyholders of non-life insurance companies. The computer program, A vehicle management data storage procedure for storing reservation data for shared cars managed by the aforementioned car-sharing business operator in a vehicle management database, linked to a vehicle ID assigned to each vehicle, and A procedure for issuing a temporary member ID to identify temporary members who can temporarily use the aforementioned shared car as a replacement vehicle, The procedure for accumulating temporary member data in the temporary member database, linked to the aforementioned temporary member ID (see Figures 4 and 5), A temporary member who has obtained the aforementioned temporary member ID has used a shared car related to their reservation data as a replacement vehicle, and the temporary member has received replacement vehicle completion data from their communication terminal indicating that the replacement vehicle is no longer needed. A vehicle data reception procedure that receives vehicle data from the aforementioned shared car, along with the vehicle ID and vehicle location data, indicating that the shared car has been returned to the designated return location after being used as a replacement vehicle. A vehicle return confirmation procedure that uses the aforementioned vehicle location data and the aforementioned replacement vehicle completion data to confirm that the vehicle corresponding to the aforementioned vehicle ID has been returned to the designated return location, A temporary ID revocation procedure is performed to revoke the temporary member ID and register it in the aforementioned temporary member database based on the return confirmation procedure for the vehicle return. This is a computer program that is to be executed by the aforementioned management server (see Figure 15).

[0046] (Variations of the third or fourth invention) A third or fourth invention may be formed as follows: In other words, the computer program is designed to have the management server execute the temporary ID revocation transmission procedure, which sends a message to the communication terminal of the temporary member indicating that the temporary member ID has been revoked using the temporary ID revocation procedure described above.

[0047] (Fifth invention) The fifth invention relates to a computer program executed on a communication terminal (contractor terminal or victim terminal) that communicates bidirectionally with a management server for managing member users and the shared cars in a car-sharing business that lends shared cars to member users who have completed member registration in advance. The computer program includes a procedure for receiving a temporary member ID issued by the aforementioned management server in order to identify temporary members who can temporarily use a shared car as a replacement vehicle for a vehicle being repaired, to the insurance policyholders of a non-life insurance company, and A repair completion notification procedure for receiving confirmation that the repair of the aforementioned vehicle has been completed, The return procedure involves using a temporary ID to return the loaner vehicle, The procedure for receiving notification of the expiration of the temporary ID from the aforementioned management server, which has confirmed the return of the loaner vehicle, This is a computer program that is executed on a communication terminal (see Figures 10 and 15).

[0048] It is also possible to transmit the computer programs relating to the third to fifth inventions from a computer storing them to other terminal devices via a communication line. They may also be provided via the internet, on a so-called cloud platform. Furthermore, computer programs relating to the third to fifth inventions can also be provided by storing them on a recording medium. Here, "recording medium" refers to a medium capable of carrying a program that cannot occupy space on its own. Examples include flexible disks, hard disks, CD-Rs, DVD-Rs, and USB memory sticks. [Effects of the Invention]

[0049] According to the first and second inventions, it was possible to provide a management server that can provide a car-sharing vehicle that can be used as a replacement vehicle to those who need one, and that can stop the use of car-sharing after the replacement vehicle is no longer needed. According to the third and fourth inventions, it was possible to provide a computer program that controls a management server that can provide a car-sharing vehicle that can be used as a replacement vehicle to a person in need of a replacement vehicle, and that can stop the use of car-sharing after the replacement vehicle is no longer needed. According to the fifth invention, we were able to provide an application program that can be executed on a terminal related to an insurance policyholder, which issues a temporary ID to a person who needs a car-sharing vehicle that can be used as a replacement vehicle, and then expires the temporary ID after the replacement vehicle is no longer needed. [Brief explanation of the drawing]

[0050] [Figure 1] This is a conceptual diagram illustrating the procedure for delivering a replacement vehicle in the event of a traffic accident. [Figure 2] This is a conceptual diagram illustrating the problems involved in delivering replacement vehicles. [Figure 3] This is a conceptual diagram illustrating the potential challenges that might arise when using car-sharing services as an alternative vehicle. [Figure 4] This is a block diagram showing the procedure for issuing a temporary corporate ID in preparation for providing a replacement vehicle to an insurance company. [Figure 5] This is a block diagram showing the procedure for issuing temporary member IDs to non-life insurance policyholders and victims. [Figure 6] This block diagram shows the process from reserving a car-sharing vehicle as a replacement vehicle to completing the reservation. [Figure 7] This block of paper will display the status until the decision on whether a replacement vehicle is available is sent. [Figure 8] This block diagram shows a scene where a car-sharing vehicle is used as a replacement vehicle. [Figure 9] This is a block diagram showing the scene where the use of a car-sharing vehicle as a replacement vehicle ends. [Figure 10] This block diagram shows the main functions performed by terminals related to non-life insurance policyholders before and after the start of using a replacement vehicle. [Figure 11] This flowchart helps distinguish whether the period for which you want to use a replacement vehicle is full-time or part-time. [Figure 12] This is a conceptual diagram illustrating the problems involved in delivering replacement vehicles. [Figure 13] This is a conceptual diagram illustrating the potential challenges that might arise when using car-sharing services as an alternative vehicle. [Figure 14] This is a block diagram showing the procedure for issuing a temporary corporate ID in preparation for providing a replacement vehicle to an insurance company. [Figure 15] This block diagram shows the scene where the use of a car-sharing vehicle as a replacement vehicle ends. [Modes for carrying out the invention]

[0051] The present invention will be described below based on the drawings and embodiments. The drawings used herein are Figures 4 to 15. Solid arrows indicate wired communication, dashed arrows indicate wireless communication, and dotted lines indicate dashed lines. Figures 1 to 3 illustrate the prior art and the problems of the present invention, and should be referred to as necessary.

[0052] (Figure 4) Figure 4 illustrates the information processing that takes place between a car-sharing management server related to a car-sharing operator, an insurance server related to a non-life insurance company that requests the car-sharing operator to provide a replacement vehicle, and a customer terminal, which is a communication terminal related to a customer who has a contract with the insurance company to receive a replacement vehicle. The information processing described here shows how a corporate non-life insurance company receives a temporary member ID, the non-life insurance ID, for its policyholders, and then assigns a sub-ID-1, which is a branch number of that non-life insurance ID, to the policyholders.

[0053] In Figure 4, after an insured person needs a replacement vehicle (typically due to a car accident, but depending on the insurance contract, this may also include a breakdown of the vehicle not caused by an accident), they are assigned a Sub-ID-1 (temporary member ID) by requesting a replacement vehicle from the non-life insurance company. Furthermore, it will be explained that there are no victims who required a replacement vehicle despite the insurance policyholder causing the accident. Therefore, in this case, no sub-ID will be issued to the victim.

[0054] Car-sharing services operate by lending out shared cars owned by the car-sharing operator to registered members. Therefore, in principle, only registered members can use the shared cars. Membership registration involves providing the car-sharing operator with personal information, driver's license information, and payment information for using the shared cars. A wide variety of car models are available, and members can prioritize their preferred vehicle when renting.

[0055] For corporate members, the member wishing to register must provide the car-sharing operator with the company's attribute information and payment information for using the shared car in advance, and receive a member ID. The corporate ID can be assigned a sub-number, so once the employees who will use the shared car are identified, the sub-number is linked to each individual employee, and registration is completed.

[0056] The management server for car-sharing operators (abbreviated as "car-sharing management server" in the diagram) manages member data in a member database (abbreviated as "member DB" in the diagram) linked to member IDs. As mentioned above, corporate members are assigned sub-numbers, which is a unique characteristic of the member database, so the individual member database and the corporate member database are constructed separately (at least conceptually).

[0057] In this system, the non-life insurance company wants to provide a replacement vehicle to its policyholders when they need one, not because its employees want to use a car-sharing service. A replacement vehicle is only needed in the event of an accident, and some policyholders may not need one until the end of their insurance contract period. In other words, the situation is different from that of a regular corporate member.

[0058] Therefore, Figure 4 shows an example of the preparations that non-life insurance companies make in advance by becoming special (exceptional from the perspective of car-sharing operators) corporate members. In Figure 4, a temporary member database for non-life insurance companies is built within the corporate member database, and non-life insurance IDs are issued as temporary member IDs. Then, for policyholders who have an insurance contract that provides a replacement vehicle in the event of an accident, a sub-number of the non-life insurance ID (non-life insurance ID-1) is assigned in response to the occurrence of an accident and the request for a replacement vehicle. For car-sharing operators, this creates an environment in which they can claim compensation from non-life insurance companies based on the use of shared cars.

[0059] First, the insurance server requests the issuance of an insurance ID, and the insurance ID issuance request mechanism sends the necessary data to the car-sharing management server to become a provisional member. The car-sharing management server receives the aforementioned data via the insurance ID issuance receiving mechanism. Then, the insurance ID issuance mechanism issues an insurance ID from the provisional member database built within the corporate member database and sends it to the insurance server.

[0060] The insurance ID can be assigned a number of sub-numbers requested by the insurance company on the insurance server. Insurance IDs sent from the car-sharing management server are received by the insurance server's insurance ID receiving mechanism and stored in the ID management database. This is for managing the IDs distributed to insurance policyholders.

[0061] An insurance policyholder who requires a replacement vehicle sends a replacement vehicle request, along with policyholder identification data, to the insurance server using a replacement vehicle request transmission means from their communication terminal (policyholder terminal). The insurance server receives the replacement vehicle request using a replacement vehicle request reception means. Based on the policyholder identification data, the policyholder database is searched, and the contract content verification means verifies whether the policyholder's contract content warrants a replacement vehicle request. If the verification confirms that the policyholder should be eligible for a replacement vehicle, the sub-ID issuance means issues a sub-ID-1 linked to a temporary ID in the ID management database, and the sub-ID transmission means sends this sub-ID-1 to the policyholder terminal.

[0062] The sub-ID transmission method sends the issued sub-ID-1 and subscriber identification data to the car-sharing management server to identify the subscriber to whom that sub-ID-1 was assigned. It is desirable that the subscriber identification data includes the subscriber's driver's license data. This is because car-sharing management companies require members to register their driver's license data as a prerequisite for lending out shared cars. If the insurance server is unable to provide the driver's license data pertaining to the policyholder, the car-sharing management server will separately request the policyholder to provide the driver's license data.

[0063] (Figure 5) Figure 5 illustrates the information processing that takes place between the car-sharing management server, the insurance server, the policyholder terminal, and the victim terminal, which is a communication terminal related to the victim of an accident caused by the policyholder. It shows the procedure for issuing temporary member IDs to the insurance policyholder and the victim.

[0064] Figure 4 illustrates a scenario where a car-sharing maintenance company and a non-life insurance company enter into a special corporate contract and issue a temporary corporate ID. On the other hand, Figure 5 shows a model where a policyholder who has a contract with a non-life insurance company, or their victim, enters into an individual contract after an accident and is issued a temporary member ID.

[0065] If a policyholder is involved in a car accident, they will send an accident report, along with their identification data, to the insurance company's server via their terminal using the accident report transmission method. If there are victims in the accident, they will also send data about those victims (such as data to identify them). The transmitted data will be received by the accident report receiving method on the insurance company's server.

[0066] On the insurance server, the policyholder database is searched based on the policyholder identification data included in the received data. Then, the contract details are checked to see if there is a contract that includes the provision of a replacement vehicle through a car-sharing service when a replacement vehicle is needed. Once the contract details have been confirmed, the temporary member ID issuance request device will send a request to the car-sharing management server, along with the subscriber identification data. If possible, the subscriber identification data should include the subscriber's driver's license data. Driver's license data is essential for using car-sharing, and it is desirable if this driver's license data can be obtained from the insurance company, as this would eliminate the need to send and receive data with the subscriber.

[0067] The aforementioned request for temporary member ID issuance is received by the temporary member ID issuance receiving means on the car-sharing management server. Then, using the temporary member database constructed within the individual member database in the member database, the temporary member ID issuance means issues the necessary temporary member IDs. In the case of Figure 5, since both the contract holder and the victim of an accident caused by the contract holder require a replacement vehicle, two temporary member IDs (temporary member ID-1, ID-2) are issued. These are then sent to the insurance server.

[0068] The temporary member ID sent from the car-sharing management server is received by the temporary member ID receiving device on the insurance server. It is then stored in the policyholder database and transmitted to the policyholder terminal and the victim's terminal, respectively, via the temporary member ID transmission device.

[0069] The subscriber receives the transmitted temporary member ID (temporary member ID-1) via the temporary member ID receiving device on the subscriber's terminal. The subscriber then uses this temporary member ID to specify the date and time when a replacement vehicle is needed and makes a reservation for a shared car provided by the car-sharing company. The same process applies to the victim.

[0070] Furthermore, if the contract with the policyholder includes a clause guaranteeing the cost of repairing the vehicle involved in the accident, the insurance company will also be contacted via the insurance server.

[0071] (Figure 6) Figure 6 illustrates the process from when a subscriber or a victim of an accident caused by a subscriber reserves a car-sharing vehicle as a replacement vehicle, with the car-sharing management server at the center of the process. Furthermore, since the procedure for victims—obtaining a temporary member ID, sending usage identification data to the car-sharing management server, and completing the reservation—is the same as for contract holders, a detailed explanation will be omitted.

[0072] Following the procedure shown in Figure 4 or Figure 5, subscribers who have obtained a sub-ID or temporary member ID will inquire about the use of a replacement vehicle with the car-sharing operator. Specifically, using their own communication terminal, the subscriber terminal, they will send data specifying their desired use, such as the date and time they wish to use a replacement vehicle, the starting location, and the type of vehicle, along with user identification data (sub-ID or temporary member ID), to the car-sharing management server.

[0073] The car-sharing management server receives user identification data and usage preference data via a replacement vehicle usage receiving means. The server then uses the member database to retrieve the user identification data and verifies whether the user is eligible to use the car-sharing service. If the user is eligible, the usage preference determination means uses the vehicle management database to determine whether or not the user can use the service based on the usage preference data. The result of the usage preference determination means is then transmitted to the subscriber's terminal via a usage preference transmission means. The subscriber's terminal receives confirmation of availability. Upon receiving confirmation that the service is available, the subscriber sends a declaration of intent to use the service to the car-sharing management server using the application submission method.

[0074] On the car-sharing server, the application receiving device receives the expression of intent to use the service. The reservation completion sending device then sends a message to the subscriber's terminal confirming the reservation. The reservation completion sending device also updates the vehicle management database with data indicating that the reservation has been completed, based on the details of the reservation request identification data. The reservation completion sending device also registers the reservation completion details in the member database, linked to the user identification data.

[0075] The aforementioned means for determining availability may also include means for calculating the utilization rate and means for extracting the date and time for using a replacement vehicle. This will be explained in detail with reference to Figure 7.

[0076] Furthermore, in many car-sharing services, when a member user determines their desired usage data, they access the vehicle management database on the car-sharing management server and select their desired starting location (station name), start time, and vehicle type. This process allows the user (contract holder) to narrow down their desired usage conditions. If the desired usage data is determined through this procedure, it is rare for the service to be deemed unavailable during the availability assessment. In this embodiment, the reason we explained that the subscriber sends the data specifying their desired usage without requiring them to narrow down the conditions is that the use of a replacement vehicle is expected to involve situations where the user desires a longer period of use (in some cases, continuous use over several days) than the temporary use period of a car-sharing member.

[0077] (Figure 7) Figure 7 shows an example of the process from determining whether a vehicle is available for use as a replacement vehicle to sending the result. Here, the aim is to improve the overall profitability of the business by extracting vehicles with low utilization rates in terms of use by members in the car-sharing system and prioritizing their allocation to replacement vehicle requests.

[0078] The vehicle management database and the means for determining availability shown in Figure 6 will be described in detail below. The vehicle management database includes a reservation database that stores data on vehicles that have already been reserved for use, and a repurposed vehicle database that stores data on vehicles reserved based on member temporary IDs or sub-IDs.

[0079] The means for determining availability includes a means for calculating the utilization rate and a means for extracting the date and time of conversion to a replacement vehicle. A method for calculating the utilization rate is a method for calculating the percentage of time that a vehicle is being rented out and generating revenue. For example, if vehicle A is rented out for an average of 6 hours a day on weekdays (Monday to Friday), then its utilization rate would be 25%.

[0080] The replacement vehicle conversion date extraction means extracts vehicles whose utilization rate, calculated by the utilization rate calculation means, is below a predetermined level, for example, 15% or less. These vehicles are then designated as replacement vehicles for priority use and registered in the replacement vehicle database. Furthermore, instead of simply identifying vehicles for repurposing based on their utilization rate, it is natural to calculate utilization rates for each day of the week, daytime utilization rates, etc., and then select vehicles (or their time slots) that are expected to be business-friendly for repurposing.

[0081] In the example shown in Figure 7, it is assumed that no matching vehicle could be extracted from the usage preference data sent from the subscriber's terminal. The figure then shows how information on replacement vehicles that closely match the conditions of the usage preference data is extracted and the result of whether or not they are available is sent to the subscriber's terminal.

[0082] For example, if the starting location does not match the subscriber's preferred usage data, but a station called "Fukuoka No. 7" is adjacent and can be provided, it will be included as a "first alternative vehicle" in the decision on whether or not it is available. Similarly, candidates such as "second alternative vehicle" and "third alternative vehicle" are also sent as part of the decision.

[0083] The reason for showing this type of output is that it is conceivable that insurance policyholders who wish to use a shared car as a replacement vehicle may want to use it continuously every day. In other words, even if an insurance policyholder requests a vehicle that does not have consecutive bookings during the same time slot, the likelihood of their request being fulfilled is low.

[0084] For illustrative purposes, the victim's terminal is not shown, but the data transmitted and received by the victim's terminal is the same as that transmitted by the subscriber's terminal.

[0085] (Figure 8) Figure 8 shows a scenario in which a customer who has completed the reservation shown in Figure 6 or Figure 7 begins using a car-sharing vehicle as a replacement vehicle.

[0086] The car-sharing management server's reservation completion transmission method sends the requested replacement vehicle data to the subscriber's terminal. The requested replacement vehicle data includes the member's temporary ID or insurance ID sub-ID related to the subscriber's terminal, and the reservation ID. The reservation ID includes the vehicle ID of the shared car related to the reservation, the vehicle type, the location where the reservation will be executed (reservation station), and the start date and time of use, and the scheduled end time of use.

[0087] The customer, carrying their contract terminal, goes to the reservation station and unlocks the vehicle (replacement vehicle) corresponding to the vehicle ID indicated in the reservation ID by transmitting the reservation ID via short-range wireless communication. Then, they begin driving the replacement vehicle.

[0088] Since the replacement vehicle is a vehicle used for the car-sharing service, it is equipped with a GPS (Global Positioning System) device. Therefore, vehicle location data is constantly acquired, and this acquired vehicle location data, along with engine data (on / off), is periodically transmitted to the car-sharing management server. The data transmitted periodically is referred to as "vehicle data." This vehicle data includes the aforementioned vehicle location data and engine data, as well as a temporary member ID indicating the driver, a vehicle ID to identify the vehicle, and a reservation ID.

[0089] Vehicle data transmitted from the replacement vehicle is received by the vehicle data receiving mechanism on the car-sharing management server, stored in the repurposed vehicle database, and also stored in the temporary member database. After being stored in the temporary member database, the rental vehicle usage commencement data transmission device sends rental vehicle usage commencement data to the insurance server as a report that the rental vehicle has been used.

[0090] The data on when a replacement vehicle is used includes the member's temporary ID or a sub-ID of the insurance ID, and the time the replacement vehicle is used. The insurance server receives this replacement vehicle usage data and stores it in the policyholder database. This allows the insurance company to know that the policyholder has successfully started using a replacement vehicle. Although not illustrated, the same applies when a victim of an accident caused by the contract holder uses a replacement vehicle.

[0091] (Figure 9) Figure 9 illustrates the main functions performed by the communication terminal for non-life insurance policyholders before and after the start of using a replacement vehicle, in relation to the car-sharing management server and the non-life insurance server. Numbers in parentheses are attached to the arrows indicating the direction of data transmission, indicating that the data is moving in that order. Note that the configuration requirements for the car-sharing management server and the non-life insurance server have already been explained, so they are kept to a minimum for illustrative purposes.

[0092] The functions performed by the subscriber terminal can be broadly categorized into two main functions: obtaining a temporary ID to qualify for using a shared car provided by the car-sharing service as a replacement vehicle (Figures 4 and 5), and completing the application for using a replacement vehicle using the obtained temporary ID (Figures 6 and 7). Although not shown in Figure 9, it also has functions to unlock the vehicle when using it as a replacement vehicle (see Figure 8) and to lock it when using it as a replacement vehicle (see Figure 10).

[0093] A policyholder who has been involved in a car accident requiring a replacement vehicle first sends policyholder identification data to the insurance server using the policyholder identification data transmission method (1). The insurance server, upon receiving the policyholder identification data, receives it using the policyholder identification data reception method and requests the car-sharing management server to issue a temporary member ID (2).

[0094] Upon receiving a request for a temporary member ID, the car-sharing management server issues a temporary member ID (or insurance ID) using the member database and the temporary member ID issuance method, and sends it to the insurance server (3). The insurance server, upon receiving the temporary member ID (or insurance ID), sends the temporary member ID (or insurance ID) to the policyholder terminal (4).

[0095] The subscriber terminal obtains a temporary member ID (or insurance ID) from the insurance server (5), and sends data specifying the desired use of a replacement vehicle to the car-sharing management server via the replacement vehicle request means (6). The car-sharing management server receives the transmitted data specifying the desired use of a replacement vehicle via the replacement vehicle request receiving means, uses the vehicle management server to determine whether it is available, and transmits the result (7). The transmitted result is received by the subscriber terminal's availability receiving means.

[0096] If the system determines that the service is available, the user sends a confirmation of their reservation from their terminal, and receives a reservation ID and other information from the car-sharing management server for the confirmed reservation (see Figure 6). However, this process is omitted in Figure 9.

[0097] The subscriber, carrying the subscriber terminal on which the acquired reservation ID is installed, goes to the start location (car-sharing station) where the replacement vehicle is prepared. Then, using the reservation ID transmission method, the subscriber sends the reservation ID and temporary member ID (or insurance ID) to the replacement vehicle, unlocks it, and begins using the replacement vehicle (8).

[0098] The car-sharing management server receives reservation IDs and vehicle data from the replacement vehicle (9), and updates the vehicle management database by linking it to the vehicle ID (10).

[0099] To easily implement the functions of the customer terminal described above, it is advisable to install dedicated application software after concluding a contract with a non-life insurance company. This dedicated application software is provided by the car-sharing operator, and it is recommended to download it.

[0100] (Figure 10) Figure 10 illustrates the scenario of ending the use of a car-sharing vehicle as a replacement vehicle. Numbers in parentheses are indicated on the arrows showing the direction of data transmission at the repair shop, insurance server, customer terminal, and car-sharing management server. The victim's terminal is also shown, but since it is the same as the customer's terminal, it will be omitted from the following explanation.

[0101] Suppose the insurance company receives notification from the repair company that the repairs to the policyholder's damaged vehicle have been completed (1). In other words, the insurance company's server receives the repair completion report from the repair completion transmission means of the communication terminal related to the completed repair company. This repair completion report contains data that identifies the policyholder.

[0102] Upon receiving the repair completion report, the insurance server registers the completion of the repair in the policyholder database based on data identifying the policyholder. It then notifies the policyholder and the car-sharing management server of the repair completion (2). Specifically, the repair completion reporting means on the insurance server transmits the repair completion to the repair completion receiving means on the policyholder terminal, and the car-sharing management server transmits the repair completion to the replacement vehicle completion receiving means.

[0103] When the car-sharing management server receives notification that the repair has been completed via the loaner vehicle completion notification method, it registers this information in the vehicle management database (3).

[0104] The subscriber drives the replacement vehicle to the car-sharing station where it should be returned after finishing its use, parks it in the designated parking space, and locks it using the locking mechanism. The locking mechanism is shown as being installed on the subscriber's terminal. From the locked replacement vehicle, the vehicle ID, vehicle location data, and data indicating that the engine has been stopped are sent to the vehicle data receiving mechanism of the car-sharing management server (4).

[0105] On the car-sharing management server, the vehicle return confirmation mechanism checks whether the return of the replacement vehicle has been completed based on the vehicle ID and vehicle location data sent from the replacement vehicle. Once the confirmation is complete, the return completion is registered in the vehicle management database and the insurance server is also notified (5).

[0106] Next, the temporary member IDs issued to policyholders through the non-life insurance company are invalidated by the temporary ID invalidation mechanism, and the data in the temporary member database is updated (7). Furthermore, a notification that the temporary member ID has expired is sent to the policyholder's terminal and the insurance server via the temporary ID expiration transmission means (8). The temporary ID expiration receiving means receives this notification on the policyholder's terminal, and the temporary member ID expires within the terminal. From this point onward, the policyholder will no longer be able to use the temporary member ID to use a replacement vehicle through car sharing.

[0107] Although not shown in the diagram, the non-life insurance company will settle the cost of providing a replacement vehicle with the car-sharing operator. The car-sharing operator will then record revenue based on the service of providing a replacement vehicle, which is not a service provided by a registered member user.

[0108] (Figure 11) Figure 11 is a flowchart showing how to distinguish between full-time and part-time use of a loaner vehicle by a customer. "Full-time" use refers to the period from when the customer needs a loaner vehicle until they no longer need it (the repair period for their own vehicle). "Part-time" use refers to using a loaner vehicle only when needed during the repair period for one's own vehicle.

[0109] First, the car-sharing management server receives the usage preference data (see Figure 6) (S1). Next, it verifies whether the received usage preference data indicates continuous use (full-time use) or not (S2).

[0110] If the requested usage data indicates part-time use, the system verifies whether there is a shared car available as a replacement vehicle at a station near the location requested by the subscriber (S3). If there is, after confirmation by the subscriber, the system sends the necessary replacement vehicle data to the subscriber (or their communication terminal) to use that shared car as a replacement vehicle (S4).

[0111] If the requested usage data indicates full-time use, the system searches for and secures a stock vehicle instead of using a regularly used shared car (S5). A "stock vehicle" is a vehicle that is not subject to reservation and is kept in the backyard (indicated as "Office Y" in the diagram) as a backup vehicle for regular vehicles. If the requested usage data indicates part-time use, a stock vehicle is also secured if there are no shared cars available as a replacement vehicle at a station near the location requested by the customer. When using a stock vehicle as a replacement vehicle, the necessary replacement vehicle data is sent to the customer (or their communication terminal) (S4).

[0112] (Figure 12) Figure 12 shows, more specifically, the situation when "S5~S6" occurs in Figure 11, where a replacement vehicle is transported from the sales office to the location requested by the customer. The numbers in parentheses above the arrows indicating the direction of data transmission indicate that the data is moving in that order. Please note that the following explanation is intended for policyholders who require a replacement vehicle, but the same applies to victims in the event of an accident caused by the policyholder.

[0113] The vehicle management database includes a regular vehicle database that stores management data for "regular vehicles," which are vehicles that are lent out to member users and vehicles that are parked at car-sharing stations in a state where they can be lent out, and a stock vehicle database that stores management data for "stock vehicles," which are stored in the back yard (referred to as "Office Y" in the diagram) as backup vehicles for regular vehicles. For clarity, it is helpful to distinguish between the regular vehicle database and the stock vehicle database, and therefore, they are shown separately in the diagram as separate database types. However, in practice, it is possible to distinguish and manage regular vehicles and stock vehicles within the vehicle management database by assigning identifiers to them.

[0114] Assume that a request for a replacement vehicle is sent from the subscriber's terminal to the car-sharing management server (1). The request for a replacement vehicle includes the member's temporary ID and data identifying the user's preference, which is received by the car-sharing management server's replacement vehicle request receiving mechanism (1). The received member's temporary ID is checked in the member database to determine whether the request is from a person who is qualified to make a request for a replacement vehicle (2).

[0115] The received data specifying the desired usage is verified by the availability determination means using vehicle management data stored in the regular vehicle database to determine whether the desired usage can be provided (4). If the result is "S5~S6" in Figure 11, it is determined that no vehicle matching the data specifying the desired usage could be found in the regular vehicle database (5).

[0116] The replacement vehicle extraction means extracts a vehicle from the stock of vehicles that matches the user preference data (6). The replacement vehicle data transmission means then transmits the replacement vehicle data, which includes a vehicle ID that identifies the extracted vehicle and a reservation ID that identifies the reservation details reflecting the user preference data mentioned above, to the sales office Y that stocks the vehicle corresponding to the vehicle ID, and instructs the sales office Y to transport the vehicle to the car-sharing station (replacement vehicle storage station S in the diagram) which is the departure point corresponding to the reservation ID (7). The communication terminal of the sales office Y receives the vehicle transport instruction, replacement vehicle data, and reservation ID via the transport instruction receiving means. In addition, between (6) and (7) above, there is an exchange between the subscriber terminal and the car-sharing management server to reserve a vehicle (stock vehicle) that matches the user's desired usage data, but this is omitted from the diagram.

[0117] Upon receiving the dispatch instruction, branch office Y dispatches the replacement vehicle to the replacement vehicle storage station S. If there is an available parking space at the replacement vehicle storage station S, the replacement vehicle can be parked there. However, there may be no available spaces. In that case, the dispatched replacement vehicle will be parked when a vehicle related to another reservation leaves the car-sharing dedicated parking space.

[0118] The replacement vehicle data transmission means also transmits the replacement vehicle data to the insurance server and the policyholder terminal (8). Using the policyholder terminal that receives the replacement vehicle data, the policyholder goes to the replacement vehicle storage station S and uses the vehicle corresponding to the vehicle ID identified by the reservation ID as a replacement vehicle. The insurance server that receives the replacement vehicle data stores it in the policyholder database, linking it to the policyholder identification data.

[0119] (Figure 13) Figure 13 shows the case where a vehicle provided as a replacement vehicle is returned after its use has ended. It illustrates the series of data processing when the repair of the vehicle related to the insurance policyholder is completed and the use of a replacement vehicle is no longer needed (particularly when a stock vehicle, as shown in Figure 12, is provided as a replacement vehicle). Please note that the following explanation is intended for policyholders who require a replacement vehicle, but the same applies to victims in the event of an accident caused by the policyholder.

[0120] Let's assume that the vehicle repair shop that repaired the contract holder's vehicle has notified the company that the repairs are complete. In other words, let's assume that the repair completion data receiving device has received the repair completion data on the car-sharing management server. The car-sharing management server that received the repair completion data stores it in the member database, linked to the temporary member ID. Although not shown in the diagram, the car-sharing management server also sends the repair completion data to the insurance server. Repair completion data is also transmitted from the vehicle repair shop to the subscriber's terminal.

[0121] The subscriber returns the rental vehicle they were using to a designated car-sharing station and sends the rental vehicle return data to the car-sharing management server. The server also receives vehicle location data linked to the vehicle ID from the rental vehicle. This allows the car-sharing management server to confirm that the vehicle has been returned (see Figure 10).

[0122] Once the car-sharing management server confirms that a vehicle has been returned, it stores return completion data linked to the vehicle ID of the returned vehicle in the vehicle management database. If a vehicle provided by a branch office has finished its use as a replacement vehicle, and that vehicle is parked in a car-sharing-only parking space at the replacement vehicle storage station, there will be a shortage of parking spaces available for vehicles that are returned to that space. Therefore, the retrieval data creation system creates retrieval data specifying which vehicle should be retrieved by which branch office and by when. The created retrieval data is then transmitted to the designated branch office.

[0123] Upon receiving the retrieval data, branch office Y dispatches staff to retrieve the vehicle used as a replacement vehicle from the replacement vehicle storage station S and return it to the stock vehicle fleet. The staff then drives the stock vehicle back to branch office Y to complete the retrieval transfer.

[0124] (Figure 14) Figure 14 also shows the case where the vehicle provided as a replacement vehicle has been returned after its use has ended. The difference from Figure 13 is that the repair completion data is sent from the vehicle repair shop via the insurance company's server, rather than the car-sharing management server. In Figure 14, the following explanation is given for policyholders who require a replacement vehicle, but the same applies to victims in the event of an accident caused by the policyholder.

[0125] The repair completion data transmitted from the vehicle repair shop is received by the insurance server's repair completion data receiving device and stored in the policyholder database. Then, the repair completion data transmission device transmits the repair completion data to the policyholder terminal and the car-sharing management server.

[0126] The process is the same as in Figure 13, starting from the point where the subscriber returns the replacement vehicle they were using to a designated car-sharing station and sends the replacement vehicle return data to the car-sharing management server. In Figure 14, the illustration of the replacement vehicle is omitted, but the process is the same as in Figure 13, where the car-sharing management server receives the vehicle ID and vehicle location data from the replacement vehicle to confirm that the vehicle return has been completed.

[0127] As shown in Figures 13 and 14, vehicles stocked at branch office Y are provided as replacement vehicles, making it easier to accommodate long-term use of replacement vehicles. It is also easier to accommodate requests from contract holders or accident victims regarding the type of vehicle and rental location for the replacement vehicle.

[0128] (Figure 15) Figure 15 shows a scenario where the use of a car-sharing vehicle as a replacement vehicle ends. Numbers in parentheses are indicated on the arrows showing the direction of data transmission in the repair shop, insurance server, customer terminal, and car-sharing management server. This is a variation of Figure 10.

[0129] In Figure 10, the car-sharing management server's means for receiving notification of the end of the loaner vehicle rental period received a repair completion report from the insurance server (Figure 10, (2)). On the other hand, in Figure 15, the car-sharing management server's means for receiving notification of the end of the loaner vehicle rental period receives a repair completion report from the subscriber's terminal (Figure 15, (2)). In this embodiment, the subscriber can easily control the timing of receiving the repaired vehicle after receiving notification of repair completion from the repair company, and the timing of returning the loaner vehicle.

[0130] The embodiments shown in Figures 4 to 15 have the following effects. Firstly, it streamlines the matching process between vehicles available from replacement vehicle providers and those desired by insurance policyholders. For both insurance companies and policyholders (including accident victims), it allows them to choose from the vehicles offered through car sharing, and if this is agreed upon at the time of the insurance contract, the search and selection of the desired vehicle can be expedited.

[0131] Secondly, for insurance policyholders (including accident victims), this streamlines the process by eliminating the need to rent a vehicle through car sharing during times when a replacement vehicle is not needed. For replacement vehicle providers and insurance companies, there are no costs associated with providing replacement vehicles during times when they are not needed, which ultimately contributes to higher insurance premiums.

[0132] Thirdly, while previously it was necessary to deliver a replacement vehicle to the location requested by the insurance policyholder (including accident victims), the hassle of delivery and collection by the replacement vehicle provider has been eliminated. In other words, the insurance policyholder only needs to go to the station where the car-sharing vehicle is parked, eliminating the need for delivery and collection by the replacement vehicle provider.

[0133] Fourthly, the occurrence of administrative problems related to insurance coverage has been reduced. Insurance policyholders may terminate their insurance coverage while receiving a replacement vehicle. This is because if the cost of the replacement vehicle is covered by the insurance policy, the insurance rating will be revised, resulting in disadvantages such as a downgrade in rating or an increase in the next premium payment. However, in the embodiment described above, the only choice required is whether to rent a car-sharing vehicle as a replacement or to stop renting it.

[0134] Fifth, it becomes possible to prioritize the use of less profitable vehicles in the car-sharing business as replacement vehicles, which could contribute to improved profitability. It also becomes possible to make effective use of stock vehicles that are waiting at the branch offices. [Industrial applicability]

[0135] The present invention has applicability in industries such as non-life insurance, replacement vehicle provision, car sharing and rental car services, parking lot operation, manufacturing of information and communication equipment necessary for parking lot operation, and software services for creating application programs used in car sharing management servers.

Claims

1. In a car-sharing business that lends vehicles to registered member users, a management server for operating the provision of replacement vehicles to policyholders of non-life insurance companies, etc. The management server is A vehicle management database that stores reservation data for shared cars managed by the aforementioned car-sharing business operator, linked to a vehicle ID assigned to each vehicle, A means for issuing temporary member IDs to identify temporary members who can temporarily use the aforementioned shared car as a replacement vehicle, A temporary member database that stores attribute data of the temporary member linked to the aforementioned temporary member ID, A temporary member who has obtained the aforementioned temporary member ID has used the shared car related to the reservation data as a replacement vehicle, and the temporary member has received replacement vehicle termination data from the insurance server, which is the server of the aforementioned non-life insurance company, indicating that the replacement vehicle is no longer needed. A vehicle data receiving means that receives vehicle data from the aforementioned shared car, along with the vehicle ID and vehicle location data, indicating that the shared car has been returned to a designated return location after being used as a replacement vehicle. A vehicle return confirmation means that uses the aforementioned vehicle location data and the aforementioned replacement vehicle completion data to confirm that the vehicle corresponding to the aforementioned vehicle ID has been returned to a predetermined return location, A temporary ID revocation means that revoks the temporary member ID and registers it in the temporary member database based on the return confirmation by the vehicle return confirmation means, A management server equipped with the necessary features.

2. In a car-sharing business that lends vehicles to registered member users, a management server for operating the provision of replacement vehicles to policyholders of non-life insurance companies, etc. A vehicle management database that stores reservation data for shared cars managed by the aforementioned car-sharing business operator, linked to a vehicle ID assigned to each vehicle, A means for issuing temporary member IDs to identify temporary members who can temporarily use the aforementioned shared car as a replacement vehicle, A temporary member database that stores attribute data of the temporary member linked to the aforementioned temporary member ID, A temporary member who has obtained the aforementioned temporary member ID has used a shared car related to their reservation data as a replacement vehicle, and a replacement vehicle termination data, which is a notification that the replacement vehicle is no longer needed, is received from the temporary member's communication terminal by a replacement vehicle termination receiving means. A vehicle data receiving means that receives vehicle data from the aforementioned shared car, along with the vehicle ID and vehicle location data, indicating that the shared car has been returned to a designated return location after being used as a replacement vehicle. A vehicle return confirmation means that uses the aforementioned vehicle location data and the aforementioned replacement vehicle completion data to confirm that the vehicle corresponding to the aforementioned vehicle ID has been returned to a predetermined return location, A temporary ID revocation means that revoks the temporary member ID and registers it in the temporary member database based on the return confirmation by the vehicle return confirmation means, A management server equipped with the necessary features.

3. The system includes a temporary ID revocation transmission means that transmits a message to the communication terminal of the temporary member indicating that the temporary ID revocation means has revoked the temporary member ID. The management server according to either claim 1 or claim 2.

4. A computer program that controls a management server for operating a car-sharing business that lends vehicles to registered member users, etc., and for providing replacement vehicles to policyholders of non-life insurance companies, etc., The computer program, A vehicle management data storage procedure for storing reservation data for shared cars managed by the aforementioned car-sharing business operator in a vehicle management database, linked to a vehicle ID assigned to each vehicle, and A procedure for issuing a temporary member ID to identify temporary members who can temporarily use the aforementioned shared car as a replacement vehicle, A procedure for accumulating temporary member data, which involves linking the temporary member ID mentioned above to the temporary member's attribute data and accumulating that temporary member's attribute data in the temporary member database, A temporary member who has obtained the aforementioned temporary member ID has used the reserved car as a replacement vehicle, and has now received replacement vehicle termination data from the insurance server, which is the server of the aforementioned non-life insurance company, indicating that the replacement vehicle is no longer needed. A vehicle data reception procedure that receives vehicle data from the aforementioned shared car, along with the vehicle ID and vehicle location data, indicating that the shared car has been returned to the designated return location after being used as a replacement vehicle. A vehicle return confirmation procedure that uses the aforementioned vehicle location data and the aforementioned replacement vehicle completion data to confirm that the vehicle corresponding to the aforementioned vehicle ID has been returned to the designated return location, A temporary ID revocation procedure is performed to revoke the temporary member ID and register it in the aforementioned temporary member database based on the return confirmation procedure for the vehicle return. A computer program that is to be executed by the aforementioned management server.

5. A computer program that controls a management server for operating a car-sharing business that lends vehicles to registered member users, etc., and for providing replacement vehicles to policyholders of non-life insurance companies, etc., The computer program, A vehicle management data storage procedure for storing reservation data for shared cars managed by the aforementioned car-sharing business operator in a vehicle management database, linked to a vehicle ID assigned to each vehicle, and A procedure for issuing a temporary member ID to identify temporary members who can temporarily use the aforementioned shared car as a replacement vehicle, A procedure for accumulating temporary member data, which involves linking the temporary member ID mentioned above to the temporary member's attribute data and accumulating that temporary member's attribute data in the temporary member database, A temporary member who has obtained the aforementioned temporary member ID has used a shared car related to their reservation data as a replacement vehicle, and the temporary member has received replacement vehicle completion data from their communication terminal indicating that the replacement vehicle is no longer needed. A vehicle data reception procedure that receives vehicle data from the aforementioned shared car, along with the vehicle ID and vehicle location data, indicating that the shared car has been returned to the designated return location after being used as a replacement vehicle. A vehicle return confirmation procedure that uses the aforementioned vehicle location data and the aforementioned replacement vehicle completion data to confirm that the vehicle corresponding to the aforementioned vehicle ID has been returned to the designated return location, A temporary ID revocation procedure is performed to revoke the temporary member ID and register it in the aforementioned temporary member database based on the return confirmation procedure for the vehicle return. A computer program that is to be executed by the aforementioned management server.

6. The management server is also instructed to execute the temporary ID revocation transmission procedure, which sends a message to the communication terminal associated with the temporary member informing them that the temporary member ID has been revoked using the temporary ID revocation procedure described above. The computer program according to claim 4.

7. In a car-sharing business that lends shared cars to registered member users, a computer program is executed on a communication terminal that communicates bidirectionally with the aforementioned member users and a management server for managing the shared cars, In order to identify temporary members who can temporarily use a shared car as a replacement vehicle for a vehicle being repaired for a non-life insurance company's policyholders, the procedure for receiving a temporary member ID issued by the aforementioned management server, A repair completion notification procedure for receiving confirmation that the repair of the aforementioned vehicle has been completed, The return procedure involves using a temporary ID to return the loaner vehicle, A temporary ID expiration reception procedure, which receives notification from the aforementioned management server that the temporary ID has expired after the return of the loaner vehicle has been confirmed, A computer program that causes a communication terminal to execute a command.

Images