JP6316088B2 - Setting device and setting program - Google Patents

Description

  The present invention relates to a setting device and a setting program for setting automobile insurance premiums.

  Conventionally, the driving time of the contracted car, the driving time zone, the driving area, the passenger's seat belt wearing situation, the driving situation such as the speed is detected and accumulated, and the accumulated information is transmitted to the insurance company server at a predetermined time interval. An insurance company server discloses a technique of calculating an insurance premium based on accumulated data and charging it by a prepaid method (see, for example, Patent Document 1 below). In addition, a technology called pay-per-use car insurance that discloses application for use and payment of an insurance premium every time it is used without limiting the target car in advance is disclosed.

JP 2005-266877 A JP 2012-3297 A

  However, the above-described conventional automobile insurance contract is a technique for setting an insurance premium based on the type of automobile license and the annual mileage, and the insurance premium cannot be changed depending on the destination and road conditions of the day. Therefore, depending on the driving content, the set insurance premium may be high or conversely low.

  An object of the present invention is to set an appropriate automobile insurance premium in units of usage times according to the traveling content.

A setting device and a setting program, which are one aspect of the invention disclosed in the present application, include a database that stores information about an accident that occurs when an insured travels on a travel date on a travel route with application of automobile insurance premiums. And having a reception process for receiving a departure point and an arrival point from the terminal , and searching for a travel route from the departure point to the arrival point based on the departure point and the arrival point received by the reception process, Based on the first calculation process for calculating the travel distance and the driving time of the travel route, and the information on the travel route, the travel distance, the driving time, and the accident obtained by the first calculation process, A second calculation process for calculating a car insurance premium when traveling, and the car insurance premium calculated by the second calculation process as the terminal And executes a transmitting process of transmitting.

  According to the representative embodiment of the present invention, it is possible to set an appropriate automobile insurance premium for each usage time according to the traveling content. Problems, configurations, and effects other than those described above will become apparent from the description of the following embodiments.

It is explanatory drawing which shows the insurance premium setting example concerning a present Example. It is explanatory drawing which shows the system configuration example of the insurance premium setting system concerning a present Example. FIG. 3 is a block diagram illustrating a hardware configuration example of the computer illustrated in FIG. 2. It is explanatory drawing which shows the example of a memory content of the weather information DB shown in FIG. It is explanatory drawing which shows the example of the memory content of road information DB shown in FIG. It is explanatory drawing which shows the example of a memory content of user information DB shown in FIG. It is explanatory drawing which shows the example of a memory content of insurance contract DB shown in FIG. It is explanatory drawing which shows the example of the memory content of accident information DB shown in FIG. It is a flowchart which shows the example of a car insurance setting process procedure from a terminal. It is explanatory drawing which shows the example of a display of a use application page. It is explanatory drawing which shows the example of a display of a vehicle type selection page. It is explanatory drawing which shows the example of a display of a driving | running route selection page. It is explanatory drawing which shows the example of a display of a driving | running route detailed page. It is explanatory drawing which shows the example of a display of a compensation information setting page. It is explanatory drawing which shows the example of a display of an insurance premium calculation result page. It is a flowchart which shows the example of a car insurance setting process procedure by a setting server.

<Insurance setting example>
FIG. 1 is an explanatory diagram illustrating an example of insurance premium setting according to the present embodiment. In this embodiment, (A) traveling distance D, (B) driving time T, (C) traveling area weather, (D) traveling area traffic jam information, (E) traveling area accident information, (F) use application By combining data such as the number of accidents of the insured ip at the time, the accident rank for the travel route R that travels at the use time is set. And the insurance premium according to the set accident rank is set. Thereby, an appropriate automobile insurance premium can be set according to the traveling content. The contractor and the insured person ip may be the same person, or the contractor and the insured person ip may be different persons.

  Here, the travel route R is a route that reaches the point c, which is the arrival point Pe, from the point a, which is the departure point Ps, via the point b, which is the transit point Pv. The travel route R is set at the time of application for use.

  (A) The travel distance D is the road distance of the travel route R searched at the time of application. (B) The driving time T is a predicted time when the insured ip travels in the car C on the travel route R searched at the time of application. (C) The weather in the travel area is the forecast information of the weather on the day of use in each of the areas Z1 to Z3 passing through the travel route R. In this example, the point a is a point in the region Z1, the point b is a point in the region Z2, and the point c is a point in the region Z3.

  (D) The road condition in the travel area is prediction information of the road condition in each of the areas Z1 to Z3 passing through the travel route R. Examples of road conditions include traffic jams and closed roads due to construction. (E) The accident information in the travel area is the number of accidents that have occurred in the past in each of the areas Z1 to Z3 passing through the travel route R. In other words, the accident information of the traveling area is information indicating whether or not the accident is a frequent accident zone.

  In the car insurance premium setting of the present embodiment, the automobile insurance premium is set for each use. The attribute data of basic policyholders and insured ip is registered in advance, and the application for use is actually made before driving, and the details of the car insurance contract (target car C, compensation details, insurance premium, travel route) After confirming R), the insured ip starts driving the car C. The car C need not be specified at the time of pre-registration.

<System configuration example>
FIG. 2 is an explanatory diagram of a system configuration example of the insurance premium setting system according to the present embodiment. In the insurance premium setting system 100, a setting server 201, a weather server 202, a road server 203, and a terminal 204 communicate with each other via a network 205 such as the Internet, a LAN (Local Area Network), and a WAN (Wide Area Network). It is a configuration that can be connected.

  The setting server 201 is a computer that sets automobile insurance premiums. The setting server 201 includes a user information DB 211, an insurance contract DB 212, and an accident information DB 213. The user information DB 211 is a database that stores information related to contractors who are users and insured persons who are subject to automobile insurance. Details of the user information DB 211 will be described with reference to FIG.

  The insurance contract DB 212 is a database that stores information on insurance contracts. The information on the insurance contract is information set by the insurance premium setting of the present embodiment described later. Details of the insurance contract DB 212 will be described with reference to FIG.

  The accident information DB 213 is a database that stores information on accidents caused by the insured ip. Information stored in the accident information DB 213 is stored in the accident information DB 213 by an input from the administrator of the setting server 201. Details of the accident information DB 213 will be described with reference to FIG.

  The weather server 202 is a computer that manages weather information. The weather server 202 has a weather information DB 220. The weather information DB 220 is a database that stores past weather information of each region (for example, the regions Z1 to Z3). Details of the weather information DB 220 will be described with reference to FIG. The weather server 202 may predict weather information of each region using information in the weather information DB 220, or may acquire weather information of each region predicted by an external site and store it in the weather information DB 220.

  The road server 203 is a computer that manages road conditions. The road server 203 has a road information DB 230. The road information DB 230 is a database that stores information related to past road conditions in each region (for example, the regions Z1 to Z3). The information on the past road condition is information indicating the road condition such as traffic jam information (for example, 10 km traffic jam) and the number of accidents at each point. Details of the road information DB 230 will be described with reference to FIG. The road server 203 may predict road conditions in each region using information in the road information DB 230. Further, the road server 203 may acquire information on road conditions in each region predicted by the external site and store the information in the road information DB 230.

  The terminal 204 is a computer used by a user of an automobile insurance contract. The terminal 204 can access only the setting server 201 and cannot access the weather server 202 and the road server 203. The terminal 204 accesses the setting server 201 to apply for user registration before the car insurance contract (the user becomes a contractor by user registration) and car insurance use application.

<Hardware configuration example>
FIG. 3 is a block diagram illustrating a hardware configuration example of the computer (hereinafter, computer 300) illustrated in FIG. The computer 300 includes a memory 301 (storage unit), a processor 302 (processing unit), a hard disk drive (HDD) 303, a display device 305 connected to the display control unit 304, a drive device 307 for the removable disk 306, and an input device 308. A communication control unit 309 for connecting to the network 205205 is connected by a bus 310. Application programs including an operating system (OS) and a Web browser are stored in the HDD 303, and are read from the HDD 303 to the memory 301 when executed by the processor 302. The processor 302 controls the display control unit 304, the communication control unit 309, and the drive device 307 as necessary to perform necessary operations. Further, data in the middle of processing is stored in the memory 301 and stored in the HDD 303 if necessary. Such a computer 300 realizes automobile insurance setting by organically cooperating hardware such as the processor 302 and the memory 301 described above with the OS and necessary application programs.

<Various databases>
FIG. 4 is an explanatory diagram showing an example of stored contents of the weather information DB 220 shown in FIG. The weather information DB 220 stores the date and time, the weather, and the temperature at regular intervals for each area. In addition to past weather and temperature, the weather information DB 220 also stores prediction information that is future weather and temperature. The weather information DB 220 is periodically updated to the latest state.

  FIG. 5 is an explanatory diagram showing an example of the contents stored in the road information DB 230 shown in FIG. The road information DB 230 stores, for each event that occurs in each area, information about the event occurrence date and time, the event occurrence point, and the road condition that is the content of the event (for example, traffic jam information at the point of occurrence (for example, 10 km traffic jam) or an accident occurrence) Or not). The generation point may be fixed in the area. The road information DB 230 is periodically updated to the latest state. Thereby, when the road server 203 (or the setting server 201) acquires the traffic jam information about a certain point, the shortest distance, the longest distance, the median, and the average of the traffic jam length (for example, 10 km) in the past traffic jam information. A value can be acquired as a predicted value. Moreover, the road server 203 (or setting server 201) can acquire the past accident occurrence frequency, when acquiring the accident information about a certain point.

  FIG. 6 is an explanatory diagram showing an example of the contents stored in the user information DB 211 shown in FIG. The user information DB 211 is a database that stores information for specifying a user. The stored contents of the user information DB 211 are set in advance by a sequence between the terminal 204 and the setting server 201. The user information DB 211 includes a contractor ID item, a contractor name item, an insured person name item, a contractor personal information item, an insured individual information item, a license item, a vehicle information item, It has an accident frequency field and a password field, and configures an entry for each contractor.

  In the contractor ID item, a contractor ID is stored for each entry. The contractor ID is identification information for uniquely identifying a contractor who is a user registered as a user. In the contractor name item, the contractor name is stored for each entry. In the insured person name item, the insured person name that is the name of the insured person ip who receives the application of the automobile insurance is stored for each entry.

  In the contractor personal information item, the contractor's personal information (for example, address, date of birth, contact information, etc.) is stored for each entry. In the insured person information item, personal information (for example, address, date of birth, telephone number, etc.) of the insured person ip is stored for each entry.

  In the license information item, information on the license of the insured ip (for example, license type, renewal date and license number) is stored for each entry.

  In the vehicle information item, information (for example, a car number and a model) related to the car C on which the insured ip can ride is stored. The value of the vehicle information item can be changed. A plurality of vehicle information may be stored.

  The number of accidents item stores the number of times the insured ip has caused an accident. The number of accidents is updated by the operation of the administrator.

  In the password item, a password is stored for each entry. The password is authenticated as the password included in the login request transmitted from the terminal 204 when the terminal 204 logs into the setting server 201.

  FIG. 7 is an explanatory diagram showing an example of the contents stored in the insurance contract DB 212 shown in FIG. The insurance contract DB 212 has a contract ID item, a contractor ID item, a fulfillment date item, a travel route information item, a driving vehicle type item, a compensation information item, a travel region item, an accident rank item, and an insurance premium item, and is used once. Configure an entry for each contract.

  The contract ID item stores a contract ID for each entry. The contract ID is unique identification information assigned when the contractor applies for the use of car insurance. Therefore, even if the contractor is the same, different contract IDs are assigned if the usage times are different.

  In the contractor ID item, the above-mentioned contractor ID is stored for each entry. Thereby, the entry of the insurance contract DB 212 and the entry of the user information DB 211 are associated with each other.

  The fulfillment date item stores the fulfillment date for each entry. The fulfillment date is the date when the car insurance contract is fulfilled, that is, the day when the insured ip drives according to the car insurance contract.

  The travel route information item stores travel route information. The travel route information is information including a departure point Ps that identifies the travel route R, one or more via points Pv and arrival point Pe, a travel distance D, and a driving time T.

  In the vehicle information item, the vehicle information of the vehicle that has been in the use time is stored as the vehicle information described above for each entry.

  The compensation information item stores a compensation range and compensation content for each entry as compensation information. The coverage is the geographical or / and temporal coverage of car insurance. Compensation content is the content related to compensation such as compensation (interpersonal, objective), insurance amount for injuries, etc.

  In the travel area information item, weather, traffic jam information, and accident information of a point on the travel route R are stored for each entry as travel area information.

  The accident rank item stores an accident rank for each entry. The accident rank is an index value indicating the likelihood of an insured person's accident in the insurance contract in the entry. For example, A, B, C, D, and E are ranked. Here, as an example, rank A is the rank that is most unlikely to cause an accident, and rank E is the rank that is most likely to cause an accident.

  The insurance premium item stores an insurance premium for each entry. The insurance premium is an amount set according to the accident rank, and is paid by the contractor. The correspondence between the accident rank and the insurance premium is related by a table (not shown).

  FIG. 8 is an explanatory diagram showing an example of the contents stored in the accident information DB 213 shown in FIG. The accident information DB 213 is a database in which entries are created for contracts in which accidents have occurred. The accident information DB 213 has an accident ID item, a contract ID item, and an accident information item, and constitutes an entry for each accident that has occurred by the insured ip. Information stored in the accident information DB 213 is information input by the administrator of the setting server 201.

  In the accident ID item, an accident ID is stored for each entry. The accident ID is identification information that uniquely identifies an accident caused by the insured ip.

  In the contract ID item, the above-described contract ID is stored for each entry. With this contract ID, the entry of the accident information DB 213 and the entry of the insurance contract DB 212 are associated.

  In the accident information item, accident information is stored for each entry. The accident information is information indicating the contents of the accident caused by the insured ip. Specifically, for example, the occurrence point, the occurrence date and time, the driving time, the travel distance, the weather, the road condition, Have. The occurrence point is the point where the accident occurred. The date and time of occurrence is the date and time when the accident occurred.

  The driving time is the time that the insured ip has driven the car according to the car insurance contract before the accident occurs. For example, the time obtained by subtracting the departure time from the occurrence time in the car insurance contract is the driving time. The travel distance is the distance that the insured ip has driven the car according to the car insurance contract before the accident occurs. For example, the road distance from the starting point to the accident point in the car insurance contract. The weather is the weather at the point where the accident occurred at the time when the accident occurred. The traffic jam information is traffic jam information when the accident occurs.

<Auto insurance setting request processing procedure from terminal 204>
FIG. 9 is a flowchart showing an example of a car insurance setting process procedure from the terminal 204. As a premise of the flow, it is assumed that user information of a user who is an operator of the terminal 204 (that is, a contractor) is already stored in the user information DB 211.

  The terminal 204 first transmits a login request to the setting server 201 (step S901). The login request includes the contractor ID and the password entered from the terminal 204 by the contractor (or insured person ip). As a result of transmitting the login request, the terminal 204 receives data from the setting server 201 (step S902). When the received data is an impossibility notification indicating that login cannot be performed (step S902: impossibility notification), the terminal 204 displays the impossibility notification on the display screen (step S903). As a result, the series of processes is completed. On the other hand, when the received data is a use application page (step S902: use application page), the terminal 204 displays the use application page on the display screen (step S904).

  FIG. 10 is an explanatory diagram showing a display example of the use application page. The use application page 1000 includes a use date / time input field 1001, a departure point input field 1002, and an arrival point input field 1003. The use date and time input field 1001 is an input field for inputting the date and time when the insured ip wants to use car insurance. The input use date and time is stored in the insurance contract DB 212 as a fulfillment date. The departure point input field 1002 is an input field for inputting a departure point where the insured ip wants to use car insurance. The arrival point input field 1003 is an input field for inputting an arrival point where the insured ip wants to use car insurance. The input departure point and arrival point are stored as travel route information in the insurance contract DB 212.

  Reference buttons 1004 and 1005 are buttons for linking to a map server (not shown) having a map database. Thereby, the departure point and the arrival point can be set in the input fields 1002 and 1003 by designating arbitrary points of the map data displayed on the display screen of the terminal 204. A new application button 1006 is a button for confirming the input contents of the use application page 1000. When the pressing of the new application button 1006 is detected, in FIG. 9, the terminal 204 transmits use application input data including the input contents of the use application page 1000 to the setting server 201 (step S905). As a result of transmitting the use application input data, the terminal 204 receives the vehicle type selection page from the setting server 201 and displays it on the display screen (step S906).

  FIG. 11 is an explanatory diagram illustrating a display example of a vehicle type selection page. The vehicle type selection page 1100 is a page where the insured ip selects a car to be driven under the application of car insurance. The vehicle type selection page 1100 includes an input area (input field and selection button) 1101 for vehicle information (number and model) of a new vehicle for driving a new vehicle. Further, the vehicle type selection page 1100 has a selection area (character string of vehicle information and a selection button of the vehicle information) 1102 of already registered vehicle information. The registered vehicle information is vehicle information read from the user information DB 211. When the pressing of any of the selection buttons is detected, in FIG. 9, the terminal 204 transmits vehicle type data including the input / selection content of the vehicle type selection page 1100 to the setting server 201 (step S907). As a result of transmitting the vehicle type data, the terminal 204 receives the travel route selection page from the setting server 201 and displays it on the display screen (step S908).

  FIG. 12 is an explanatory diagram showing a display example of a travel route selection page. The travel route selection page 1200 is a page that displays one or more travel route data. The travel route data 1201 includes map data 1202 for displaying the travel routes R1 and R2, types of the travel routes R1 and R2 (toll road priority, general road priority, etc.) 1203, a selection button 1204, and a detail button 1205. Have. When the pressing of the detail button 1205 is detected, the terminal 204 transmits a travel route detail page acquisition request to the setting server 201, and the setting server 201 transmits a travel route detail page to the terminal 204 in response to the acquisition request. To do. As a result, the terminal 204 displays the travel route detail page on the display screen.

  FIG. 13 is an explanatory diagram showing a display example of a travel route detail page. The travel route detail page 1300 in FIG. 13 is the travel route detail page 1300 for the general road priority travel route R2 shown in FIG. The travel route detail page 1300 includes map data 1302 and detailed information 1303. The map data 1302 displays weather information of a point a as a departure point, a point b as a transit point, and a point c as an arrival point.

  The detailed information 1303 includes, for example, the travel distance of the travel route R2 displayed in the map data 1302, the drive time (predicted value), the weather in the travel region, the traffic congestion information (predicted value) in the travel region, and the accident information in the travel region. including. The detailed information 1303 is information that the setting server 201 reads from the weather information DB 220 or the road information DB 230, embeds in the travel route detail page 1300, and transmits it to the terminal 204.

  In addition, in FIG. 12, when the pressing of the selection button 1204 is detected, in FIG. 9, the terminal 204 transmits travel route data 1201 corresponding to the selection button 1204 to the setting server 201 (step S909). As a result of transmitting the travel route data 1201, the terminal 204 receives the compensation information setting page from the setting server 201 and displays it on the display screen (step S910).

  FIG. 14 is an explanatory diagram illustrating a display example of a compensation information setting page. The compensation information setting page 1400 is a page where the insured ip sets compensation information that is the application content of car insurance. The compensation information setting page 1400 includes a compensation range setting area 1401 and a compensation content setting area 1402. In the compensation range setting area 1401, compensation in a section or / and compensation in a period can be set. Further, in the compensation content setting area 1402, it is possible to set content relating to compensation such as a compensation application target (person, objective), insurance amount for injury, and the like. When the pressing of the transmission button 1403 is detected, in FIG. 9, the terminal 204 transmits compensation data including the setting content of the compensation information setting page 1400 to the setting server 201 (step S911). As a result of transmitting the compensation data, the terminal 204 receives the insurance premium calculation result page from the setting server 201 and displays it on the display screen (step S912).

  FIG. 15 is an explanatory diagram showing a display example of the insurance premium calculation result page. As shown in FIG. 15, the insurance premium calculation result page 1500 displays various information 1501 set in FIGS. 10 to 14. In addition, the insurance premium calculation result page 1500 displays an insurance premium calculation result 1502. Insurance premium calculation result 1502 includes, for example, accident rank and insurance premium. When the pressing of the use application button 1503 is detected, in FIG. 9, the terminal 204 sends to the setting server 201 use application data indicating that the user agrees to the contents shown in the insurance premium calculation result page 1500 and applies for use. Transmit (step S913). As a result of transmitting the use application data, the terminal 204 receives a completion notification from the setting server 201 and displays it on the display screen (step S913). As a result, the series of processes is completed.

<Example of Car Insurance Setting Processing Procedure by Setting Server 201>
FIG. 16 is a flowchart illustrating an example of a car insurance setting process procedure by the setting server 201. First, the setting server 201 receives the login request transmitted from the terminal 204 in step S901 (step S1601). The setting server 201 performs contractor authentication processing using the contractor ID and password included in the login request. Specifically, for example, the setting server 201 identifies an entry having a contractor ID that matches the contractor ID included in the login request from the user information DB 211. Then, the setting server 201 compares the password included in the login request with the password included in the specified entry, and determines whether or not they match. If they do not match, the authentication fails (step S1602: No), and the setting server 201 transmits a disapproval notification indicating login disapproval to the terminal 204 (step S1603).

  On the other hand, if they match, the authentication is successful (step S1602: Yes), and the setting server 201 transmits the use application page 1000 shown in FIG. 10 to the terminal 204 (step S1604). When use application input data is transmitted from the terminal 204 in step S905, the setting server 201 receives the use application input data (step S1605) and stores it in the memory 301. Then, the setting server 201 reads the contractor's vehicle information from the user information DB 211, and transmits the vehicle type selection page 1100 in which the read vehicle information is embedded as shown in FIG. 11 (step S1606).

  Further, when the vehicle type data is transmitted from the terminal 204 in step S907, the setting server 201 receives the vehicle type data (step S1607) and stores it in the memory 301. Then, the setting server 201 calculates travel route information (step S1608). The travel route information is, as described above, the departure point, the transit point, and the arrival point that define the travel route, the travel distance on the travel route, and the driving time on the travel route. The setting server 201 can calculate a plurality of types of travel route information such as toll road priority and general road priority.

  Thereafter, the setting server 201 transmits a travel route selection page 1200 including travel route information to the terminal 204 (step S1609). When the travel route data is transmitted in step S909, the setting server 201 receives the travel route data (step S1610) and stores it in the memory 301. Then, the setting server 201 transmits the compensation information setting page 1400 illustrated in FIG. 12 (step S1606).

  Next, when compensation data is transmitted in step S911, the setting server 201 receives the compensation data (step S1612) and stores it in the memory 301. Then, the setting server 201 calculates an insurance premium (step S1613). Here, an example of calculating the insurance premium will be specifically described.

  The setting server 201 refers to the map data and calculates the travel distance and the drive time of the travel route R specified by the travel route data stored in the memory 301. In addition, the setting server 201 acquires the use date and time included in the use application input data stored in the memory 301 and the departure point, the waypoint, and the arrival point included in the travel route data stored in the memory 301. Then, the setting server 201 acquires weather information (weather and temperature prediction information) of the area including the acquired points in the time zone from the weather information DB 220. In addition, the setting server 201 refers to the road information DB 230 and calculates traffic information (predicted value of the length of traffic) and accident information (number of accidents) at each acquired point. The calculation of the traffic jam information and the accident information may be executed by the road server 203, and the calculation result may be acquired by the setting server 201. In addition, the setting server 201 acquires the past number of accidents of the insured ip corresponding to the contractor from the user information DB 211.

  Note that the weather in the weather information may be digitized according to the type of weather. For example, the numerical value is increased when the weather is bad, or the numerical value is increased when the temperature is too high (for example, the temperature corresponding to a very hot day) or too low. In addition, the weight for each acquired value is set in advance. Then, the setting server 201 obtains a sum of weighted acquired values, that is, a weighted linear sum, sets the accident rank of the insured person ip based on the weighted linear sum, and stores it in the memory 301. Store. Here, as an example, it is assumed that the higher the sum is, the lower the accident rank of A to E (the lowest is E rank). Then, the setting server 201 reads the insurance premium corresponding to the set accident rank using a table (not shown) and stores it in the memory 301.

  Thereafter, the setting server 201 transmits an insurance premium calculation result page 1500 in which the information stored in the memory 301 is embedded to the terminal 204 (step S1614). When use application data is transmitted in step S913, the setting server 201 generates contract data based on the information embedded in the insurance premium calculation result page 1500 and stores it as an entry in the insurance contract DB 212 (step S1616). ). Thereafter, the setting server 201 transmits a completion notification to the terminal 204 (step S1617), and ends the series of processes.

  Thereafter, the insured ip will drive in accordance with the car insurance contract at the use date (performance date), but if it does not cause an accident, the insured ip is considered to have been driven in accordance with the car insurance contract.

  On the other hand, when the insured ip causes an accident, the setting server 201 creates a new entry in the accident information DB 213 by an operation input by the administrator. In addition, the setting server 201 increases the number of accidents of the entry of the insured person ip in the user information DB 211 by 1 by an operation input by the administrator.

  In the example described above, the insurance premium is calculated using the weather information DB 220 and the road information DB 230. However, the insurance premium may be calculated using the accident information DB 213. Specifically, for example, for each entry in the accident information DB 213, the setting server 201 determines whether the travel route includes the occurrence point of the accident information DB 213, whether the use date and time is the time zone of the occurrence time of the accident information DB 213, Whether the time is longer than the driving time of the accident information DB 213, the driving distance is longer than the driving distance of the accident information DB 213, the weather matches the weather of the accident information DB 213, or the road condition matches the road condition of the accident information DB 213 The contents such as are numerically weighted.

  In addition, the setting server 201 acquires the past number of accidents of the insured ip corresponding to the contractor from the user information DB 211. The setting server 201 obtains the sum, that is, the weighted linear sum for each entry of the accident information DB 213, and sets any one of the maximum value, the minimum value, the median value, and the average value as the accident rank setting target. Then, the setting server 201 sets the accident rank of the insured ip according to the weighted linear sum that is the setting target, and stores the accident rank in the memory 301. Then, the setting server 201 reads the insurance premium corresponding to the set accident rank using a table (not shown) and stores it in the memory 301. Thereby, the automobile insurance premium can be set according to the driving situation similar to the driving situation where the accident occurred.

  Moreover, since the entry stored in the accident information DB 213 is an entry specified by the contract ID, the number of entries in the accident information DB 213 is small at the beginning of operation. Therefore, until the predetermined number of entries in the accident information DB 213 is accumulated, as described above, the insurance premium is calculated using the weather information DB 220 and the road information DB 230, and after the predetermined number of entries in the accident information DB 213 are accumulated. The insurance premium may be calculated using the accident information DB 213. In the above-described insurance premium calculation, at least the travel route, the travel distance of the travel route, and the driving time may be used.

  Thus, according to the present embodiment, it is possible to set an appropriate automobile insurance premium for each usage time. The present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the scope of the appended claims. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and the present invention is not necessarily limited to those having all the configurations described. A part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Moreover, you may add the structure of another Example to the structure of a certain Example. In addition, for a part of the configuration of each embodiment, another configuration may be added, deleted, or replaced.

  In addition, each of the above-described configurations, functions, processing units, processing means, etc. may be realized in hardware by designing a part or all of them, for example, with an integrated circuit, and the processor realizes each function. It may be realized by software by interpreting and executing the program to be executed.

  Information such as programs, tables, and files that realize each function can be stored in a storage device such as a memory, a hard disk, and an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, and a DVD.

  Further, the control lines and the information lines are those that are considered necessary for the explanation, and not all the control lines and the information lines that are necessary for the mounting are shown. In practice, it can be considered that almost all the components are connected to each other.

100 insurance premium setting system 201 setting server 202 weather server 203 road server 204 terminal 211 user information DB
212 Insurance Contract DB
213 Accident Information DB
220 Weather Information DB
230 Road information DB
1000 Usage application page 1100 Car model selection page 1200 Travel route selection page 1400 Compensation information setting page 1500 Insurance premium calculation result page

Claims (7)

A setting device having a memory for storing a program, a processor for executing the program, and an interface for controlling communication between terminals,
It has a database that stores information about accidents that occurred when the insured traveled on the driving date and time with the application of automobile insurance premiums,
The processor is
A receiving process for receiving a departure point and an arrival point from the terminal;
A first calculation process of searching a travel route from the departure point to the arrival point based on the departure point and the arrival point received by the reception process, and calculating a travel distance and a driving time of the travel route; ,
A second calculation process for calculating a car insurance premium when traveling on the travel route based on the travel route, travel distance, driving time and information on the accident obtained by the first calculation process;
A transmission process for transmitting the automobile insurance premium calculated by the second calculation process to the terminal;
The setting apparatus characterized by performing. In the reception process, the processor receives a travel date and time for traveling on the travel route,
In the second calculation process, the processor calculates a car insurance premium for traveling on the travel route based on weather information of a point on the travel route at the travel date and time received by the reception process. The setting device according to claim 1. In the reception process, the processor receives a travel date and time for traveling on the travel route,
In the second calculation process, the processor calculates a car insurance premium for traveling on the travel route based on information on a road condition at a point on the travel route at the travel date and time received by the reception process. The setting device according to claim 1, wherein:   The setting device according to claim 3, wherein the information on the road condition is information on a traffic jam at a point on the travel route.   The setting device according to claim 3, wherein the information related to the road condition is the number of accident occurrences at a point on the travel route.   The said calculation process WHEREIN: The said processor calculates the automobile insurance premium in the case of driving | running the said driving | running route based on the past accident frequency | count of the insured person who drives | runs the said driving | running route. Item 2. The setting device according to Item 1. A setting program for causing a processor to execute setting of automobile insurance premiums,
The processor is accessible to a database that stores information relating to an accident that occurred when the insured traveled on the travel date and time under the application of a car insurance premium;
In the processor,
Receive processing to receive the departure and arrival points from the terminal,
A first calculation process of searching a travel route from the departure point to the arrival point based on the departure point and the arrival point received by the reception process, and calculating a travel distance and a driving time of the travel route; ,
A second calculation process for calculating a car insurance premium when traveling on the travel route based on the travel route, travel distance, driving time and the accident obtained by the first calculation process;
A transmission process for transmitting the automobile insurance premium calculated by the second calculation process to the terminal;
A setting program for executing

Images