Information processing device, information processing system, and information processing method

Abstract

To properly update the contract details of an insurance for an automobile.SOLUTION: An information processing device accessible to a database that manages the contract details of a vehicular insurance obtains first data that represents the ex-post addition of a first vehicular component to a first vehicle, and when there is a contracted vehicular insurance for the first vehicle and the first data is obtained, registers, in the database, the fact that the first vehicular component is now covered by the insurance.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to automobile insurance. [Background technology]

[0002] A system for centrally managing information about automobile insurance is known. As an invention related to this, for example, Patent Document 1 discloses a system for calculating insurance premiums according to the driving characteristics of a driver. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-128486 Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure aims to appropriately update the contents of automobile insurance contracts. [Means for solving the problem]

[0005] A first aspect of the present disclosure is an information processing device having a control unit that performs the following operations: acquiring first data indicating that a first vehicle component has been subsequently added to a first vehicle; and, if a first vehicle insurance contract covering the first vehicle exists and the first data has been acquired, registering in a database that manages the contract contents of the first vehicle insurance that the first vehicle component has become covered by the first vehicle insurance.

[0006] A second aspect of the present disclosure is an information processing system including a first device that manages the contract details of a vehicle insurance policy corresponding to a first vehicle, and a second device corresponding to a base where at least vehicle components are installed on the first vehicle, wherein when a first vehicle component is subsequently added to the first vehicle, the second device transmits first data identifying the first vehicle component to the first device, and when a first vehicle insurance policy covering the first vehicle exists and the first device acquires the first data, the first device registers in a database that manages the contract details of the first vehicle insurance that the first vehicle component is now covered by the first vehicle insurance.

[0007] A third aspect of the present disclosure is an information processing method including the steps of acquiring first data indicating that a first vehicle component has been subsequently added to a first vehicle, and, if a first vehicle insurance contract covering the first vehicle exists and the first data has been acquired, registering in a database managing the contract contents of the first vehicle insurance that the first vehicle component has become covered by the first vehicle insurance.

[0008] Another aspect of the present disclosure is a program for causing a computer to execute the above-described information processing method, or a computer-readable storage medium that non-temporarily stores the program. [Effects of the Invention]

[0009] According to the present disclosure, the contents of automobile insurance contracts can be appropriately updated. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an outline of an insurance system according to a first embodiment. [Figure 2] A diagram explaining the overview of car insurance. [Figure 3] FIG. 2 is a diagram illustrating the configuration of a management server and a base server. [Figure 4] 10 shows an example of contract data stored in the management server. [Figure 5] 1 is an example of component data stored on a management server. [Figure 6] An example of work data sent from the base server. [Figure 7] 10 is a flowchart of a process executed by a base server. [Figure 8] 10 is an example of a screen for the base server to obtain information about work. [Figure 9] 10 is a flowchart of a process executed by a management server. [Figure 10] 10 is an example of contract data according to the second embodiment. [Figure 11] FIG. 10 is a diagram illustrating an outline of an insurance system according to a third embodiment. [Figure 12] 11 is a flowchart of a process executed by a management server in the third embodiment. [Figure 13] Example of data to identify the insurance company with which a policy is in place for a given vehicle. DETAILED DESCRIPTION OF THE INVENTION

[0011] In recent years, an environment has been developed that makes it easy to upgrade vehicle components. For example, by replacing the onboard computer (onboard terminal or electronic control unit), it is now possible to easily add functions to a vehicle. In addition to replacing hardware, it is also now possible to add functions by updating software.

[0012] In this way, by upgrading the vehicle after the fact, the value of the vehicle can be increased. On the other hand, automobile insurance often does not take into account the subsequent increase in the value of the vehicle. For example, the limit of insurance payments made by automobile insurance generally decreases as the number of years since the new car registration passes. This is because the value of the vehicle is calculated based on its current market value.

[0013] Therefore, if you upgrade a vehicle component after the fact, there may be a discrepancy between the actual value of the vehicle and the vehicle insurance amount set at the time of signing the car insurance contract. Also, it may happen that the vehicle component added after the fact is not covered by the vehicle insurance. In such a case, it may happen that you are not able to compensate all the damages caused in the event of an accident. The information processing device according to the present disclosure solves such a problem.

[0014] An information processing device according to a first aspect of the present disclosure is characterized by having a control unit that executes the following: acquiring first data indicating that a first vehicle component has been added to a first vehicle after the fact; and, if a first vehicle insurance contract covering the first vehicle exists and the first data has been acquired, registering in a database that manages the contract contents of the first vehicle insurance that the first vehicle component has become covered by the first vehicle insurance.

[0015] The information processing device is a device that can access a database related to automobile insurance (vehicle insurance) contracts. Vehicle insurance is insurance that compensates for damage caused to a vehicle. The database may store vehicle insurance coverage for each of multiple vehicles. The first data may be received from an external device or the like, or may be input by a user of the device. The external device may be, for example, a device corresponding to a repair shop that adds vehicle components. The information processing device installs a first vehicle component in the first vehicle based on the acquired first data. The first vehicle may be added after the fact (i.e., after the first vehicle is manufactured).

[0016] The first vehicle component does not necessarily have to be a hardware component. For example, the first vehicle component may be software running on an on-board computer. In this case, the first vehicle component may be new software or a newer version of software than the previously installed software. In other words, "the subsequent addition of the first vehicle component" may mean "the installation of new software" or "the installation of upgraded software."

[0017] If an automobile insurance (vehicle insurance) contract covering a first vehicle exists and a first vehicle component is subsequently added to the first vehicle, the control unit registers in the database that the first vehicle component is now covered by insurance. This process may be, for example, a process of updating the upper limit of the insurance amount based on the assessed value of the first vehicle component, or a process of explicitly indicating that the first vehicle component is included in the insurance coverage.

[0018] With this configuration, even if the first vehicle is upgraded later, the increase in value can be covered by the vehicle insurance.

[0019] In addition, when the control unit receives second data indicating that a second component has been removed from the first vehicle, the control unit may register in the database that the second component is no longer covered by insurance.

[0020] The control unit may also recalculate the insurance premium for the vehicle insurance policy to which the first vehicle component has been added as an insured item. The insurance premium may increase based on an increase in the value of the first vehicle.

[0021] Whether or not it is desirable to add the first vehicle component to the insurance coverage may vary depending on the vehicle owner. For example, if the first vehicle is a leased vehicle, it is preferable to insure the entire vehicle, including the added components. On the other hand, if the first vehicle is owned by a user, whether or not to insure the added vehicle components may depend on the user's judgment. Therefore, the control unit may further acquire third data indicating whether the first vehicle is a leased vehicle, and perform different processing based on the third data. For example, the registration may be performed if the first vehicle is a leased vehicle, and may not be performed if the first vehicle is not a leased vehicle.

[0022] In addition, if the first vehicle is a leased vehicle, the lease fee for the first vehicle may be recalculated based on the recalculated insurance premium. In addition, if the first vehicle is a leased vehicle, the insurance coverage period for the first vehicle components may be set to the lease period of the first vehicle as the upper limit.

[0023] Specific embodiments of the present disclosure will be described below with reference to the accompanying drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, etc. described in each embodiment are not intended to limit the technical scope of the disclosure to those configurations.

[0024] (First embodiment) An outline of the insurance system according to the first embodiment will be described with reference to FIG. The insurance system of this embodiment is composed of a device (management server 100) that manages automobile insurance contracts for multiple vehicles, and a device (base server 200) that corresponds to a vehicle base where vehicle components are installed, etc.

[0025] The management server 100 is a device that manages data related to automobile insurance contracts. The management server 100 may be a device under the control of an insurance company. 2, automobile insurance includes multiple insurances such as personal injury insurance, bodily injury liability insurance, property damage liability insurance, and vehicle insurance. In this embodiment, automobile insurance contracts include vehicle insurance contracts. The management server 100 holds information about the contents of a specified insurance contract concluded for a specified vehicle (for example, the contents of the guarantees that are provided for in a vehicle insurance contract).

[0026] The base server 200 is a server device associated with a base where installation, removal, or replacement of vehicle components is performed (hereinafter referred to as a vehicle base). In this example, the vehicle components are assumed to be hardware components, but the vehicle components may also be software components. In this case, the vehicle base may also be a base where software running on an onboard computer is added, updated, or updated. In this case, the installation, removal, and replacement of vehicle components can be rephrased as software installation, uninstallation, and update, respectively. A vehicle base is, for example, a vehicle manufacturing plant, a repair shop, a car dealer, etc. When work is performed on a specific vehicle, the base server 200 generates data indicating details of the work (hereinafter, work data) and transmits the data to the management server 100.

[0027] FIG. 3 is a diagram showing in more detail the components of the management server 100 and the base server 200 included in the insurance system according to this embodiment.

[0028] First, the management server 100 will be described. The management server 100 stores a database that manages the details of automobile insurance contracts for multiple vehicles under its management, and updates the database based on the work data received from the base server 200.

[0029] The management server 100 can be configured as a computer having a processor such as a CPU or GPU, a main memory such as RAM or ROM, and an auxiliary memory such as an EPROM, a hard disk drive, or removable media. The auxiliary memory stores an operating system (OS), various programs, various tables, etc., and the programs stored therein are loaded into the working area of ​​the main memory and executed. By controlling each component through the execution of the programs, various functions consistent with predetermined purposes can be realized, as described below. However, some or all of the functions may be realized by hardware circuits such as ASICs or FPGAs.

[0030] In this embodiment, the management server 100 may be configured to be able to execute a web server for interacting with the base server 200. In this case, for example, the base server 200 can input and output information by accessing a web service using a browser. Note that the management server 100 may provide a service by means other than a web server. For example, the management server 100 may execute a service that interacts with dedicated application software installed on the base server 200 using a predetermined protocol.

[0031] The management server 100 includes a control unit 101 , a storage unit 102 , and a communication unit 103 . The control unit 101 is an arithmetic unit that manages the control performed by the management server 100. The control unit 101 can be realized by an arithmetic processing unit such as a CPU. The control unit 101 is configured to have, as a functional module, a data update unit 1011. The functional module may be realized by executing a stored program by a CPU.

[0032] The data update unit 1011 updates the contents of the vehicle insurance contract among the automobile insurance contracts based on the work data received from the base server 200. Specifically, the data update unit 1011 executes one of the following processes.

[0033] (1) When a new vehicle component is installed on the subject vehicle, the process of adding the vehicle component to the insurance coverage. When a new vehicle component is installed on the subject vehicle, the data update unit 1011 performs processing to add the newly installed vehicle component as a subject of vehicle insurance. When a vehicle component is newly installed in a vehicle and the vehicle component is fixed or secured to the vehicle, the vehicle component is considered to be part of the vehicle and is covered by insurance. Therefore, in such a case, the data update unit 1011 records data in the database indicating that the newly installed vehicle component is part of the vehicle related to the contract (i.e., is covered by vehicle insurance).

[0034] (2) When an existing vehicle component is removed, the process of removing the vehicle component from the insurance coverage. On the other hand, if a vehicle component is removed, the vehicle component is no longer considered to be part of the vehicle. In such a case, the data update unit 1011 records data in the database indicating that the removed vehicle component is no longer part of the vehicle related to the contract (i.e., is no longer covered by the vehicle insurance).

[0035] (3) The process of updating insurance coverage when vehicle components are replaced. When a vehicle component is replaced, the previous vehicle component is no longer covered by insurance, and the replaced vehicle component becomes the new insurance subject. In such a case, the data update unit 1011 records data in the database that clearly indicates that the vehicle components that make up the vehicle have changed (i.e., the insurance subject has changed).

[0036] The storage unit 102 is configured to include a main storage device and an auxiliary storage device. The main storage device is a memory in which the programs executed by the control unit 101 and the data used by the control programs are expanded. The auxiliary storage device is a device in which the programs executed by the control unit 101 and the data used by the control programs are stored.

[0037] The storage unit 102 also stores contract data 102A and component data 102B.

[0038] The contract data 102A is data relating to insurance contracts for vehicles under management. 4 is an example of the contract data 102 A. As shown in the figure, the contract data 102 A is configured to have fields for a contract ID, a vehicle ID, contract details, and accessory information. The contract ID field is a field in which an identifier that uniquely identifies an automobile insurance contract is stored. The vehicle ID field is a field in which an identifier that uniquely identifies a vehicle is stored. The contract details field is a field for storing data related to the contract details of the automobile insurance contract, such as whether or not there is personal injury insurance, the amount, and scope of the insurance, whether or not there is bodily injury insurance, the amount, and whether or not there is property damage insurance, the amount, and whether or not there is vehicle insurance, and the amount, and such data can be exemplified. The accessory information field stores an identifier that identifies a vehicle component attached to the target vehicle. For example, if a vehicle component is installed later, the accessory information field stores the identifier of the vehicle component. If a vehicle component is registered as an accessory, the vehicle component becomes covered by vehicle insurance as an element that constitutes the vehicle. Note that if the target vehicle component is software, the accessory information field may store the identifier of the software, or the identifier of the hardware that runs the software.

[0039] The component data 102B is data relating to vehicle components that can be added to the target vehicle. Fig. 5 shows an example of the component data 102B. As shown in the figure, the component data 102B is configured to have fields for a component ID and an evaluation price. The component ID field is a field in which an identifier that uniquely identifies a vehicle component is stored. The appraisal value field is a field in which the appraisal value (insurance amount) of the target vehicle component is stored.

[0040] The above-mentioned data may be constructed by a database management system (DBMS) program executed by a processor that manages data stored in a storage device. In this case, the data may be, for example, a relational database.

[0041] The communication unit 103 is a communication interface for connecting the management server 100 to a network. The communication unit 103 includes, for example, a network interface board and a wireless communication interface for wireless communication.

[0042] Next, the base server 200 will be described. The base server 200 is a device installed at a base where work to install and remove vehicle components is performed, and when such work is performed on a vehicle, it transmits data regarding the content of the work to the management server 100. The work is performed, for example, when an order is received from a user.

[0043] Like the management server 100, the base server 200 can be configured as a computer having a processor such as a CPU or GPU, a main memory such as a RAM or ROM, and an auxiliary memory such as an EPROM, a hard disk drive, or removable media.

[0044] The base server 200 includes a control unit 201 , a storage unit 202 , a communication unit 203 , and an input / output unit 204 . The control unit 201 is an arithmetic unit that controls the base server 200. The control unit 201 can be realized by an arithmetic processing unit such as a CPU. The control unit 201 is configured to have two functional modules: a data acquisition unit 2011 and a data transmission unit 2012. Each functional module may be realized by executing a stored program by a CPU.

[0045] The data acquisition unit 2011 generates work data based on the content of the input made by the staff member at the vehicle base. Fig. 6 is a diagram showing an example of the content of the work data. As shown in the figure, the work data includes fields for vehicle ID, work date, vehicle base ID, work type, and component ID. The vehicle ID field stores an identifier that uniquely identifies the vehicle to be worked on (for example, the chassis number or VIN (Vehicle Identification Number)). The work date field stores The date the work was performed is stored. The vehicle base ID field stores an identifier that uniquely identifies the vehicle base where the work was performed. The work type field stores either "Installation (of a vehicle component)," "Removal (of a vehicle component)," or "Replacement (of a vehicle component)." The component ID field stores the identifier of the vehicle component to be worked on.

[0046] The data transmission unit 2012 transmits the work data generated by the data acquisition unit 2011 to the management server 100 .

[0047] The storage unit 202 is configured to include a main storage device and an auxiliary storage device. The main storage device is a memory in which programs executed by the control unit 201 and data used by the control programs are expanded. The auxiliary storage device is a device in which programs executed by the control unit 201 and data (including working data) used by the control programs are stored.

[0048] The communication unit 203 is a communication interface for connecting the base server 200 to a network. The communication unit 203 includes, for example, a network interface board and a wireless communication interface for wireless communication. The input / output unit 204 is a unit that accepts input operations performed by a user (staff member) of the base server 200 and presents information to the user. The input / output unit 204 may include, for example, an interface with an external display, a keyboard, a mouse, and the like.

[0049] 3 is an example, and all or part of the illustrated functions may be performed using a dedicated circuit. Also, programs may be stored or executed using a combination of a main memory and an auxiliary memory other than those illustrated.

[0050] Next, the processes executed by each device included in the insurance system will be described in detail. 7 is a flowchart showing the processing executed by the base server 200 (data acquisition unit 2011). The processing shown in FIG. 7 is executed when work is performed on a vehicle at a predetermined vehicle base.

[0051] First, in step S11, information about the work content is acquired. In this step, for example, a vehicle identifier and a work type are acquired. In this example, the work type is one of "(vehicle component) installation," "(vehicle component) removal," and "(vehicle component) replacement." Note that installation of a vehicle component here means new installation of the vehicle component. This information may be input via a screen such as that shown in Fig. 8. In the example of Fig. 8, reference numeral 801 denotes a GUI component for inputting a vehicle identifier. Reference numeral 802 denotes a GUI component for selecting a work type.

[0052] In step S12, it is determined whether the work type is "mounting," "removing," or "replacing."

[0053] If the work type is "installation," the process proceeds to step S13, where work data indicating that a vehicle component has been newly installed is generated. The work data includes an identifier of the newly installed vehicle component. If the work type is "removal," the process proceeds to step S14, where work data indicating that the vehicle component has been removed is generated. The work data includes the identifier of the removed vehicle component. If the work type is "replacement," the process proceeds to step S15, where work data indicating that a vehicle component has been replaced is generated. The work data includes identifiers of the removed vehicle component and the newly installed vehicle component. If the vehicle component is software, the identifier may be a combination of the software identifier and version.

[0054] The notification data generated by the base server 200 is transmitted to the management server 100 and processed by the data update unit 1011 . FIG. 9 is a flowchart of the database update process performed by the management server 100 (data update unit 1011).

[0055] First, in step S21, the notification data transmitted from the base server 200 is acquired. Next, in step S22, it is determined whether the work type is "mounting," "removing," or "replacing."

[0056] If the work type is "installation," the process proceeds to step S23, where the newly installed vehicle component is added as an insurance target. Specifically, for the corresponding record in the contract data 102A, the identifier of the newly installed vehicle component is stored in the accessory information.

[0057] If the work type is "removal," the process proceeds to step S24, where the removed vehicle component is excluded from the insurance coverage. Specifically, for the corresponding record in the contract data 102A, the identifier of the removed vehicle component is deleted from the accessory information.

[0058] If the work type is "replacement," the process proceeds to step S25, where the removed vehicle component is excluded from the insurance coverage and the newly installed vehicle component is added as an insurance coverage. Specifically, for the corresponding record in the contract data 102A, the identifier of the removed vehicle component is deleted from the accessory information, and the identifier of the newly installed vehicle component is added.

[0059] As described above, in the insurance system according to the first embodiment, the management server 100 performs a process of registering vehicle components as parts of the vehicle based on the work performed on the vehicle. This allows all vehicle components currently equipped on the vehicle to be covered by the vehicle insurance.

[0060] In the first embodiment, the management server 100 performed a process to change the vehicle insurance coverage based on the details of the work performed on a specific vehicle. Meanwhile, when the vehicle insurance coverage changes, the insurance premium may also change. Therefore, the management server 100 may execute a process to recalculate the vehicle insurance premium based on the updated contents of the database. This process may be executed, for example, when the process shown in FIG. 9 is completed. The increase or decrease in the insurance premium may be determined, for example, based on the assessed value of the target vehicle component recorded in the component data 102B. Furthermore, the management server 100 may execute a process to reflect the recalculated insurance premium in the contract.

[0061] (Second embodiment) In the first embodiment, as shown in FIG. 4, the vehicle components covered by the vehicle insurance are On the other hand, vehicle insurance contracts may be managed by a maximum amount, rather than by registering each item covered by insurance one by one. In the second embodiment, the amount set as the upper limit of vehicle insurance for a specific vehicle is changed when a vehicle component is installed or removed.

[0062] In the second embodiment, vehicle insurance contracts are managed based on a maximum amount. Fig. 10 shows an example of contract data 102A in the second embodiment. The vehicle insurance amount field is a field that stores the maximum amount of insurance payable under the target contract. The maximum amount of insurance payable is usually the assessed value of the entire vehicle (including any installed vehicle components). In addition, in the second embodiment, when the data update unit 1011 receives work data, it recalculates the assessed value of the entire vehicle, which changes as vehicle components are installed or removed, and updates the vehicle insurance amount based on the calculated amount.

[0063] The valuation value of the entire vehicle, which changes with the installation or removal of vehicle components, can be determined based on the valuation values ​​of the vehicle components recorded in component data 102B, for example. For example, in step S23, the data update unit 1011 performs a process of adding the assessed value of the newly added vehicle component to the vehicle insurance amount. Also, in step S24, the data update unit 1011 performs a process of subtracting the assessed value of the removed vehicle component from the vehicle insurance amount. Also, in step S25, the data update unit 1011 performs a process of subtracting the assessed value of the removed vehicle component from the vehicle insurance amount and adding the assessed value of the added vehicle component to the vehicle insurance amount. In this way, it is possible to define the subject of vehicle insurance by amount.

[0064] (Third embodiment) In the first and second embodiments, when there is a change in the configuration of the vehicle components mounted on the vehicle, the subject of the vehicle insurance is changed unconditionally. On the other hand, there may be cases where this is not desirable depending on the vehicle owner. For example, if the vehicle is leased to the user by a business (e.g., a leasing company), it is preferable to cover all vehicle components with insurance. On the other hand, if the vehicle is owned by the user himself, it is up to the user to decide whether to insure any vehicle component.

[0065] In order to address this, the third embodiment is an embodiment in which it is determined whether or not a vehicle component of a vehicle is to be covered by insurance, based on the owner of the vehicle. 11 is a schematic diagram of the insurance system according to the third embodiment. As shown in the figure, the insurance system according to the third embodiment further includes a vehicle server 300. The vehicle server 300 is a device that manages owner information for multiple vehicles under the management of the system. In this embodiment, the vehicle server 300 uses a vehicle identifier (e.g., VIN, Vehicle Identification Number, etc.) as a key to obtain information about the owner of the vehicle. Search and provide.

[0066] FIG. 12 is a flowchart of the processing executed by the management server 100 (data update unit 1011) in the third embodiment. First, in step S31, an inquiry is made to the vehicle server 300 to obtain information about the owner of the target vehicle. The inquiry can be made using an identifier that uniquely identifies the target vehicle. The information about the owner of the target vehicle can be, for example, either "the owner and user match" or "the owner and user do not match." If it can be determined whether the target vehicle is a rented vehicle, the vehicle server 30 0 may provide other data.

[0067] In step S32, it is determined whether the owner and user match. If the owner and user match, the process proceeds to step S33, where the user is prompted to select whether to change the insurance coverage in accordance with an increase or decrease in vehicle components. If a positive determination is made, the process proceeds to step S21, where the above-described process is executed. The same applies if the owner and user do not match in step S32. In all other cases, the process ends.

[0068] According to the third embodiment, when the owner of the vehicle is different from the user (i.e., when the vehicle is on loan), it is possible to automatically execute a process to change the insurance subject.

[0069] In the third embodiment, the management server 100 may also execute a process of recalculating the vehicle insurance premium based on the updated contents of the database. Furthermore, if the subject vehicle is a leased vehicle, the usage fee (e.g., monthly usage fee) for the leased vehicle may change in accordance with a change in the insurance premium. Therefore, the management server 100 may execute a process of recalculating the usage fee for the leased vehicle based on the recalculated insurance premium. In addition, in the third embodiment, the insurance period for the corresponding vehicle component may be set to match the lease period of the target vehicle or to a period up to the end of the lease.

[0070] (Variation) The above-described embodiment is merely an example, and the present disclosure can be modified and implemented as appropriate within the scope that does not deviate from the gist of the disclosure. For example, the processes and means described in this disclosure can be freely combined and implemented as long as no technical contradiction occurs.

[0071] Furthermore, in each embodiment, the management server 100 stores a database relating to automobile insurance contracts, but the database does not necessarily have to be stored in the management server 100. For example, if a vehicle user has contracts with multiple underwriting companies for automobile insurance, the database may be stored by multiple server devices. In this case, the management server 100, upon receiving the work data, may identify the database device of the corresponding insurance company and send an instruction to update the database to that database device. For this reason, the management server 100 may store data that associates the vehicle identifier with information for identifying the insurance company that provides the automobile insurance (such as the insurance company identifier, the identifier or IP address of the database device corresponding to the insurance company), as shown in FIG. 13.

[0072] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by a single device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.

[0073] The present disclosure can also be realized by supplying a computer program that implements the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium that can be connected to the system bus of the computer, or may be provided to the computer via a network. The non-transitory computer-readable storage medium may be, for example, a magnetic disk (floppy disk (registered trademark) This includes any type of disk, such as a hard disk (HDD), optical disk (CD-ROM, DVD, Blu-ray), read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic card, flash memory, optical card, or any type of medium suitable for storing electronic instructions. [Explanation of symbols]

[0074] 100 Management Server 101,201 Control unit 102,202...Storage section 103,203···Communications Department 200...Base server 204...Input / output section

Claims

1. Obtaining first data indicating a subsequent addition of a first vehicle component to a first vehicle; When a first vehicle insurance contract covering the first vehicle exists and the first data is acquired, registering in a database managing the contract details of the first vehicle insurance that the first vehicle component is covered by the first vehicle insurance; An information processing device having a control unit that executes the above.

2. The insurance company further includes the database storing vehicle insurance coverage for each of a plurality of vehicles. The information processing device according to claim 1 .

3. The control unit further acquires second data indicating that a second component has been removed from the first vehicle; If the first vehicle insurance contract covering the first vehicle exists and the second data is acquired, registering in the database that the second component is no longer covered by insurance; The information processing device according to claim 1 .

4. The control unit recalculates the insurance premium for the first vehicle insurance based on the contents of the database after the registration. The information processing device according to claim 1 .

5. The control unit further acquires third data indicating whether the first vehicle is a leased vehicle. The information processing device according to claim 4 .

6. If the first vehicle is a leased vehicle, The control unit recalculates the lease fee for the first vehicle based on the recalculated insurance premium. The information processing device according to claim 5 .

7. The control unit If the first vehicle is a leased vehicle, the registration is performed, and if the first vehicle is not a leased vehicle, the registration is not performed.

7. The information processing device according to claim 5 or 6.

8. If the first vehicle is a leased vehicle, The control unit sets an insurance coverage period for the first vehicle component with the lease period of the first vehicle as an upper limit. The information processing device according to claim 7 .

9. a first device for managing the details of a vehicle insurance contract corresponding to a first vehicle; a second device corresponding to a site where at least a vehicle component is installed on the first vehicle; An information processing system comprising: the second device transmits, when a first vehicle component is subsequently added to the first vehicle, first data identifying the first vehicle component to the first device; When a first vehicle insurance contract covering the first vehicle exists and the first device receives the first data, the first device registers in a database managing the contract details of the first vehicle insurance that the first vehicle component is covered by the first vehicle insurance. Information processing system.

10. the second device further transmits second data to the first device indicating that a second component has been removed from the first vehicle; When the first device has the first vehicle insurance contract covering the first vehicle and receives the second data, the first device registers in the database that the second component is no longer covered by insurance. The information processing system according to claim 9 .

11. The first device recalculates the insurance premium for the first vehicle insurance based on the contents of the database after the registration. The information processing system according to claim 9 .

12. the first device further receives third data indicating whether the first vehicle is a leased vehicle; The information processing system according to claim 11.

13. If the first vehicle is a leased vehicle, the first device recalculates the lease fee for the first vehicle based on the recalculated insurance premium; The information processing system according to claim 12.

14. The first device comprises: If the first vehicle is a leased vehicle, the registration is performed, and if the first vehicle is not a leased vehicle, the registration is not performed.

14. The information processing system according to claim 12 or 13.

15. If the first vehicle is a leased vehicle, the first device sets an insurance coverage period for the first vehicle component up to the lease period of the first vehicle; The information processing system according to claim 14.

16. A method of claim 15, further comprising: acquiring, by a computer, first data indicating that a first vehicle component has been subsequently added to a first vehicle; When a first vehicle insurance contract covering the first vehicle exists and the first data is acquired, the computer registers in a database managing the contract details of the first vehicle insurance that the first vehicle component is covered by the first vehicle insurance; An information processing method, including:

17. The method of claim 16, further comprising the step of: said computer obtaining second data indicating that a second component has been removed from said first vehicle; When the first vehicle insurance contract covering the first vehicle exists and the second data is acquired, the computer registers in the database that the second component is no longer covered by insurance.

17. The information processing method according to claim 16.

18. The method further includes a step in which the computer recalculates the insurance premium for the first vehicle insurance based on the contents of the database after the registration.

17. The information processing method according to claim 16.

19. The method further includes a step of the computer obtaining third data indicating whether the first vehicle is a leased vehicle.

19. The information processing method according to claim 18.

20. If the first vehicle is a leased vehicle, the computer recalculates the lease fee for the first vehicle based on the recalculated insurance premium; 20. The information processing method according to claim 19.

Images